home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-20
/
paket51.zip
/
MANUAL2@.EXE
/
MANUAL2.DOC
< prev
Wrap
Text File
|
1992-04-06
|
224KB
|
6,573 lines
PART V - Messages in the paKet system
Overview
This is a list of messages in the paKet system. They are listed in
alphabetic order. For the Online Manual, this Section has been divided
into several sub sections to make it all a bit easier to manage.
Each message is categorised with one of the following codes:
I - Information level
W - Warning level
E - Error level
C - Errors with "Press Enter to Continue"
D - Dialogue (always appear regardless of level set)
Information level messages are routine messages that do not require any
action on your part.
Warning level messages are usually some more serious or unexpected event
but one that paKet can cope with.
Errors are serious problems that you really should know about!
Most messages will stay on the screen for about 3 seconds but those
which either require some action on your part or which might take a
little longer to digest will appear as 'C' type messages. For these, you
press the <Enter> key when ready to continue.
You may choose to hide the Information level messages once you have had
some experience with the paKet system. The 3 second "delay" could become
tiring for those routine Information messages that you know about and
expect anyway. You could even hide the Warning messages if you choose
but I would not recommend it! Refer to the Configuration -
Miscellaneous options section for details on setting the Message Level.
The Dialogue messages are those that require some data input, for
example where you are asked to enter a file name.
Messages emanating from the Contest Mode have not been included here.
These messages apply only to that rather unique and seldom used sub
system. They are quite self explanatory if you are using that mode, but
would require some understanding of the Contest Mode to make much sense.
I have decided to omit them here to help reduce confusion.
Page 91
A to C
W. A smaller version of this file exists.
I will attempt a paKet-Protocol Recovery
This message could appear if a Binary File is being transferred to our
system and both stations are equipped to handle the advanced paKet
Protocol.
The situation that causes this message is where the file being
transferred already exists on our system but our file is shorter than
the one about to be sent by the other station. This could happen if
an earlier file transfer was aborted for some reason and so our file
would be incomplete.
This message informs you that paKet is asking the other station to
check the details to see if a Recovery is possible.
D. Abort, Retry, Ignore <R>
An error has occurred. You have three options: A, R or I...
A(bort) the program. If you select this option, paKet will simply give
up, and return to DOS. As this is a rather serious step, paKet will
seek your confirmation that this is really what you want to do by
prompting you with the following question:
Aborting paKet and returning to DOS... Are you sure? <N>
If you then reply "Y", everything stops and you will be returned to
the DOS Prompt. It is nice to have a way out in case of a really
serious problem but I expect this option would be rarely required.
R(etry) the operation that caused the error. This is the default
response so if you simply press <Enter>, paKet will assume a Retry.
In most cases I hope this will get you going again. For example it
might be a diskette problem such as "door not closed", "write
protect tab", etc so you can attend to the problem, select Retry and
things should proceed normally.
I(gnore) the problem. An error message is like pain: it is there for
a reason and should not be ignored. But if you are sure you know
what the problem is and choose to ignore it, you can select this
option and paKet will try to continue despite the error. However, do
this at your own peril and don't call me if you get into trouble!
I. Appending to existing file ..."
This message appears when you are starting the Log file or are writing
the Flashback buffer to disk if paKet finds the specified file is
already on the disk.
paKet will preserve the contents of that file and will write the new
data to the end of this file.
No action required.
Page 92
E. ASCII file command must be AD, AC or AU
The Script file you have just loaded contains a command beginning with
A but it is not one of the valid ASCII file transfer commands.
The Script has been aborted.
D. Buffer Search
Please enter the search string -
When you wish to search backwards through the Flashback buffer for a
particular string of characters, this message will prompt you for the
data to search for.
This is not case sensitive so it doesn't matter if the data is in
upper or lower case, if it is spelt the same it will be matched!
Refer to the section on the <Alt-F> and <Alt-L> keys for further
discussion on this faciity.
E. CFG file error
This error will appear immediately after you attempt to start the
program if there is something wrong with the PAKET.CFG file. It will
not even appear in a pop-up window because those windows will not have
been created yet.
The error could be caused by an old version of the CFG file still in
the current directory. To run paKet version 5, you need a CFG file for
version 5 - it is not the same CFG file as that used in earlier
versions.
If you do not have a CFG file for version 5 or if it has been
corrupted in some way you should either restore a backup copy of the
CFG file (if there is a PAKETCFG.BAK file available, try that) or
reinstall paKet version 5.
I. Clearing TNC's XOFF
This message appears in response to your <Alt-Q> command to manually
override and reset the system's XOFF condition. This would be used
only if you are using Software Handshaking and then it would be a rare
occasion indeed that you might need this command.
Refer to the <Alt-Q> command in the Special Keys section of this
Manual for more information on this command.
If, after the XOFF condition is cleared, the TNC is still unable to
accept any more data, it will send another <XOFF> and paKet will
reenter the XOFF state.
Page 93
I. Closing log file (filename)
This is a message to confirm the Log File is now being closed.
This message could appear after you close the Log File with the <F2>
key or if the file is closed automatically by the AUTO log function
when a station is Disconnected.
No action is required unless you want to continue logging, in which
case you should manually reactivate the Log File with the <F2> key.
D. COMx is not installed. Try another? (Y/N)
When paKet starts, one of the first things it does is to set up the
Computer's Serial port. It tries to initialise the port you have
specified in your Configuration but if that port is unavailable, this
message appears to give you the opportunity to try another one.
This condition should rarely occur but is possible if you have changed
your Computer's hardware or if you have copied a Configuration File
from another system.
Anyway, no harm is done as paKet will cycle through all the Serial
Ports until it finds the one you wish to use.
You should check the rest of the Configuration, especially the Serial
Port details once the system starts up. If the Port number was wrong,
it is possible other parameters will need adjustment too.
W. Confirming...Connected to (callsign)
After pressing <Alt-V> to verify the connected status, this message
will appear if the TNC agrees with the callsign already displayed in
the Communications Window Header line.
No action required.
W. Confirming...Not Connected
After pressing <Alt-V> to verify the connected status, this message
will appear if there is currently no connection and the TNC has simply
confirmed this.
No action required.
Page 94
D to H
D. Deleting (filename) - Are you sure? (Y/N)
If you attempt to delete a file, paKet will ask for confirmation
before it performs the deletion. You have one final chance!
Enter "Y" to carry out the deletion.
E. Disk error on drive X
Unfortunately this means just what it says.
This error condition is returned by the DOS operating system. The
causes are many and varied so you should perform the usual checks to
try to identify the cause. Typically the error is related to the lack
of space on a disk or diskette, or perhaps a diskette drive door was
opened.
If there really is a fault with the disk you will be getting similar
error messages when you are running other programs. In that case
specialist attention is required.
Refer to the I/O Error message for some of the types of error that may
be identified. This added information is supplied by DOS so check the
DOS documentation for further information.
Refer to the description on the "Abort, Retry, Ignore" message for
discussion on the options available.
W. Displayed Callsign changed to match the TNC
After pressing <Alt-V> to verify the connected status, this message
will appear if the TNC indicates we are connected to a station other
than that indicated in the current window's Communications Window
Header.
No action required.
D. Enter a DOS command, or press Enter for a DOS window.
>
When you want to exit to DOS to perform some program or DOS command
you can do it in one of two ways:
1. You may enter the command into the message window beside the
">" prompt.
If you do this, the command will be executed (if possible) and
you will be invited to "Press any key to continue" before paKet
resumes where it left off. The "Press any key to continue"
message appears briefly over the DOS display to allow you time to
peruse the result of the job and to read any messages etc that
may have come from the DOS command.
2. Press <Enter> instead of entering a command, and the screen will
be cleared before control is passed over to DOS and the familiar
Page 95
DOS Prompt.
When you have finished the DOS operations, type EXIT to return to
paKet. Do NOT type PAKET again as the system will attempt to
load a second copy of paKet into memory!
Please keep in mind that paKet is still in memory at this stage,
gathering any incoming data that may be sent from the TNC while you
are doing your DOS jobs. So you will have considerably less free
memory for your other DOS programs and may even find some will not run
due to insufficient memory. The only remedy for this, I am afraid, is
to return to paKet and exit the program so you can release the memory
occupied by paKet.
D. Enter new Path\Filename for (filename)
When you select a file to be Renamed or Moved to another directory
(with the <Alt-R> key), paKet will ask for the new name.
In response to this message, enter the new filename or, if you wish to
move it to another sub directory, enter the full path details. For
example:
\PAKET\BINARY\UTILS\USEFUL.COM
If the Rename or Move cannot be performed you might see one of the
following self explanatory messages:
No such file or directory
I can't do that.
Maybe that file exists?
I can't MOVE to a different device!
D. Enter Path:
When you choose to "Enter file name manually" from the Directory
Window you will be asked to enter the details in this Message Window.
Any valid file name may be entered here, including a drive and/or
directory together with the desired filename.
E. Error closing the log file
The operating system has detected an error while trying to close the
Log File.
Check the usual things (available space, diskette drive, etc) and be
warned that you could have lost some of the log file with this error.
Processing will continue without the Log File.
C. Error saving Configuration. No changes saved.
If you make any changes to paKet's Configuration, the changes are
automatically saved to disk, but if this message occurs, the latest
changes to the Configuration have NOT been saved.
Processing continues, but you should check your system to see why the
error occurred. The possible causes are many and varied but if you are
Page 96
not having other problems this could be as simple as running out of
space.
E. Error setting new directory
When the Directory Window is on the screen, you may change directories
by highlighting a sub directory entry (shown as "<DIR>") then pressing
<Enter>. The system will change to that directory and will then
display the contents of that new sub directory.
This error message occurs when the system is unable to change to the
new directory. As you would usually be changing by pointing to the
displayed directories, this error is most likely to be some sort of
disk or diskette error,
E. Error writing to file being Received - now closed
A disk write error has occurred while receiving an ASCII file.
The file is now closed but is probably incomplete. You should check
your computer system to see what might have caused the problem.
Typically this error is caused by a lack of space on the disk or, if a
diskette is being used, check the diskette is not write protected and
the drive door is closed.
When you have corrected the problem, you can try the file transfer
again.
D. EXIT to DOS?
Press "Y" to Confirm
After pressing <Alt-X> to exit the program this message will appear
asking for your confirmation that this is what you really want. It is
so easy to press the wrong key (I have done it often).
If you enter "Y" the paKet program will close down and control returns
to the DOS prompt (or to the Menu if you loaded paKet from a Menu).
Anything else and paKet resumes whatever it was doing when you pressed
<Alt-X>.
C. Failed to make window
There are over 20 different windows used by the paKet system and there
is some memory allocation and initialisation required to set these up.
The most likely problem if this message appears is Insufficient Memory.
Refer to the Insufficient Memory message for further information.
E. File has no data
You have selected a file to be sent to another station but this file
is empty!
Page 97
E. File write error
While performing a Binary File transfer a disk error has occurred. As
various checks are usually performed before the transfer begins, I am
afraid this message does suggest you have a hardware problem.
Maybe if you are using diskettes the problem is simply a matter of the
drive door being open?
E. Hey, we have got more data than the file size expected!
I can't handle that, so I will abort the transfer
This should not happen because the system will be expecting the exact
file size as indicated in the directory. But just in case...
The problem could happen if you try to send a file that is currently
open and being used for something else. For example if you try to send
the Log File that paKet is currently using. But you wouldn't do that
would you?
I. Housekeeping...tidying up the PMS DataBase...
From time to time, when you are using the Sysop PMS Menu (refer the
<Alt-M> key) paKet will perform some internal housekeeping to minimise
any wastage of space in the PMS sub-system. This message appears
briefly to inform you of this housekeeping.
Page 98
I can't...
E. I can't append to the file
A disk error has occurred after choosing to append to the existing
file. At this stage, we know the file exists so the most likely cause
would be a lack of space or a genuine hardware error. I hope you are
out of space!
E. I can't create a new PMS DataBase
I'll try again next time.
While doing some housekeeping on the PMS DataBase, paKet tried to
create a new file to contain the "cleaned up" PMS but got a disk
error.
This housekeeping can wait till next time - it is not critical - so
processing continues. You should check it out as soon as possible to
see what the problem is.
E. I can't create the file
An attempt was made to create a new data file but it failed.
You could check to see there is sufficient space available and if you
are using the Root directory, ensure there are sufficient directory
entries available.
If using diskette, ensure the diskette is not write protected and the
diskette is inserted in the drive with the door closed.
It should be quite obvious which file paKet is trying to create
because of other messages that will be displayed and because it is
probably the result of some command you have given that the file is
being created anyway.
If the new file is one specified in the Configuration, for example the
Connect File, check the details in the Configuration - it may be you
have specified a drive or directory that does not exist.
E. I can't delete this entry
You may delete a normal FILE from a Directory Window, but you may NOT
delete a ReadOnly, Hidden or System File, a Sub Directory, nor a
Volume Label!
C. I can't do that. Maybe that file exists?
The system returned an error condition when trying to rename a file.
Typically this could be because the new name you gave is a file that
already exists in that directory. The Rename/Move function is not
like a COPY command - it will not overwrite an existing file.
Page 99
E. I can't find COMMAND.COM
You are in big trouble! The system could not find COMMAND.COM and you
will not be able to run other DOS jobs without it!
Usually DOS can find it via the COMSPEC parameter, or maybe in the
current directory or via the PATH statement.
W. I can't find (filename). I'll create a new one.
When you first use the <Alt-C> facility to Connect to another station,
paKet will fail to find a Connect File and will produce this message
to let you know it is creating a new one.
You can enter as many station details as you wish into this window and
it will be automatically saved to disk using the "filename" specified.
Next time that file should be found and the message will no longer
appear.
There is a possibility the filename is incorrect in paKet's
Configuration in which case the message will serve as a warning that
you are not accessing the correct file. Or perhaps the file is on
diskette and the appropriate diskette is not in the drive. If so, you
can delete or ignore the new file just created, and insert the correct
diskette.
E. I can't find (filename)
This error message appears after paKet is asked to process this data
file but the file could not be found.
It is most likely to appear after you have manually entered a file
name.
Try the operation again, specifying the correct file name, not
forgetting to specify a path (drive and subdirectory) if necessary.
The error could also appear after selecting a file which is specified
incorrectly in the Configuration. For example if the location of the
TNC Help file is not correctly recorded in the Configuration this
message will appear when you press <F10> to see the TNC Help file. In
this case, select the Configuration (<Alt-Z>, then 8) and make the
necessary corrections before trying the operation again.
If you are in REMOTE Mode and the other station requests a file
transfer, this message will be sent to that other station if the
specified file could not be found.
E. I can't find that message!
You have entered a PMS command but the message number you have
specified does not exist.
Reenter the command with the correct message number. You could perform
a List command ("L") to see the available messages.
Page 100
E. I can't find the (dir) directory.
This message will appear if you have manually entered a file name and
path but the directory could not be found.
Try the operation again with the correct name.
E. I can't find the program to run
The "program" in this case could be a program name you have entered at
the DOS command line provided by paKet's <F9> DOS exit.
Another possibility is the system could not find the program to Edit
or to Display a data file if you have used the <Alt-E> or the <Alt-D>
commands.
If the message occurs after you select <Alt-E>, check paKet's Online
Configuration - Files/Directories and correct the System Editor entry
before trying the operation again.
If the message occurs after you select <Alt-D>, check paKet's Online
Configuration - Files/Directories and correct the "Command to list a
file" entry before trying the operation again.
E. I can't MOVE to a different device!
When moving a file with the <Alt-R> key, the system will not actually
copy the data, it simply adjusts the directory entry. As different
drives have different directories, a "move" is not possible between
drives. You will have to copy the file to the new drive then (if
desired) delete the file on the original drive. Use the COPY command
from the DOS Gateway (refer <F9> key).
E. I can't Rename/Move this entry
You may Rename or Move a normal FILE in a Directory Window, but you
may NOT Rename or Move a Hidden or System File, a Sub Directory, nor a
Volume Label!
D. I can't see CTS signal on the Serial Port!
Would you like to try Software Handshaking? (Y/N)
You might need to refer to the discussion on Hardware vs Software
Handshaking in the Technical Section of this Manual if you have
difficulty understanding what this is all about.
If you are using Hardware Handshaking the CTS signal should be present
when the program starts but paKet has found that signal "missing".
It is possible the cable used to connect the TNC to the Computer does
not have this CTS line connected. Such cables are quite common and if
you have one of these, you must change to Software Handshaking.
Page 101
If you reply "Y" paKet will change it's Configuration to Software
Handshaking and processing will continue. Please ensure the TNC's
XFLOW command is set ON if you use Software Handshaking - this is
especially important if you are doing any file transfers.
If you reply "N" paKet will attempt to continue in Hardware
Handshaking mode, although without a CTS signal it will be unable to
send to the TNC! Usually you would select this option after you have
been able to restore the CTS line and then processing will continue
normally.
Page 102
I to L
E. I did not get the expected response from the TNC
So, I am not too sure whether we are connected or not!
When you press <Alt-V> to verify the TNC's connected status. paKet
issues a command to the TNC and interrogates its response but in this
case the expected response was not received.
The displayed callsign is not changed.
If this happens more than once, it may be the TNC is not responding
for some reason so you should check that and ensure it is still
working for normal commands, then try the <Alt-V> again.
E. I don't have room for all the help file
This error message means there are more index entries in the file than
I have allowed for.
It is unlikely you will see this message, but if you do it is because
someone has modified the Help file since I released it. Naughty!
C. Insufficient memory
There are thousands of places within paKet (well quite a few anyway)
that could issue this dreaded message.
Earlier versions of paKet had a separate message from each routine
that wanted some more memory but couldn't get it. This is nice, but
contributes to the problem as each of these separate messages occupy
some memory! While there are a couple of situations where the system
can continue despite the lack of memory, in most cases paKet will
refuse to continue! So, it doesn't really matter which part of paKet
wants the extra memory, you've still got the problem.
paKet will perform some internal overlays to reduce the demands but
will still require a system with 384KB at a pinch, and preferably more
for a workable system.
In addition to the program itself, memory is required for data storage
and buffers. Most of this storage is dynamically allocated from free
memory after the program is loaded and it is in this area that you
will most likely strike the "Insufficient memory" message. Examples
include allocation of memory for the data input buffers, and for the
Flashback buffers. You can configure up to 10 windows each of which
can have up to 32 KB for input buffer and up to 64KB Flashback buffer.
Try getting all that into 384KB, in fact try getting it all into 640KB!
If you have any EMS memory available, paKet will automatically detect
it and will use some of that for its internal overlays, but most of
the memory required comes from the Base 640KB.
Try to conserve as much memory as possible because even if paKet runs
quite happily in the available memory, you might still need more if
you want to run some external program from within paKet. For example,
editing a file will add to the memory demands as the system will have
to load the chosen Editor program then load the data file you want to
Page 103
edit. Or if you take the DOS exit (refer <F9> key) you might find
there is not enough memory left, after paKet has taken its lot, to run
your DOS commands.
There are some things you can do to overcome this "Insufficient
memory" problem:
1. If you are one of the few remaining diehards who are running an
IBM or compatible system with less than 640KB RAM, then the
solution is easy: "buy some more memory!"
2. Reduce the memory demands from within paKet by:
a. configuring fewer Communications Windows (I find 3 plenty
for my operation). Each of these will consume some memory
overheads and if you don't really need all 10 windows you
can save some memory by reducing the number.
b. configuring smaller buffers for Input and Flashback buffers
in each of the Communication Windows.
Most of the time I use only the first window - it is only
on relatively rare occasions the second window gets used,
the third window hardly ever. So I tend to configure larger
buffers for the first window and reduce the others.
3. Reduce other memory overheads such as TSRs.
Many people do not realise that Menu programs, Shells, and the
like that provide a "launching pad" for their programs, usually
remain in memory while their other program is running. You should
run paKet from the DOS prompt, by all means from a BATch file,
but not from a Shell or Menu.
And any other TSRs such as DOS's Print Spooler, Mouse drivers,
various Pop-Up utilities such as Calendars and Phone Diallers,
all consume some memory even if they are not currently being
used. There are techniques available for some systems now to load
these things in High Memory (eg the latest versions of MS-DOS and
DR-DOS, as well as other products such as QEMM provide this
"load-high" facility). If you can, load as much as possible into
High Memory to relieve the pressure on the Base 640K. Otherwise
try removing any unwanted TSRs and drivers before loading paKet.
E. Insufficient space for this file.
When receiving a Binary File, paKet will check the file size (once it
is known) and verify there is sufficient space on the drive to hold
the file.
This will avoid wasted time by aborting the transfer before it starts
if the file is not going to fit.
E. Invalid argument
This message will appear if you have specified an invalid DOS command.
Check the command and reenter.
Page 104
E. Invalid colour in PAKET.CFG - (colour)
There is something wrong with your PAKET.CFG file.
As this file is maintained by the program itself, it is likely the
problem has been caused by some manual editing. If you can, restore an
earlier, working copy of the CFG file and try again. Otherwise you
should reinstall the paKet system and start again.
E. Invalid FLAG command in Script
The Script file you have just loaded contains a command beginning with
F which suggests a Flag command but the syntax is invalid.
Refer to the section on Script Processing for syntax details.
E. I/O Error - Bad Request
E. I/O Error - Data Error (CRC)
E. I/O Error - Drive not ready
E. I/O Error - General failure
E. I/O Error - Printer out of paper
E. I/O Error - Read fault
E. I/O Error - Sector not found
E. I/O Error - Seek Error
E. I/O Error - Unknown command
E. I/O Error - Unknown error type
E. I/O Error - Unknown media type
E. I/O Error - Unknown unit
E. I/O Error - Write fault
E. I/O Error - Write protected
An error has occurred and paKet has attempted to identify the
particular error. These errors are documented in your computer's
Operating System documentation and are reasonably descriptive of the
problem.
In most cases you will know what is causing the error as you will have
just performed some function, for example you will have requested a
directory display from a diskette, or you will have attempted to use
the printer.
Refer to your DOS system documentation for further information on any
action to be taken.
And refer to the description on the "Abort, Retry, Ignore" message for
discussion on the options available.
I. Loading Manual from (filename)
When selecting the Online Manual, this message appears to let you know
it is working and it confirms the name of the file it is loading the
information from.
It can take a few seconds, longer if loading from diskette, so you are
reassured the system is still working.
Page 105
If you get an "Insufficient memory" message here, it will be followed
by:
Continuing without Online Manual...
paKet will then continue with normal communications but, of course, in
that case you will not be able to view the Online Manual.
I. Loading (TNC-Helpfile-name) ...
When you first select the TNC Help File, the index to the TNC commands
is loaded into memory. This can take a few seconds, more if you are
loading it from diskette, and this message appears so you can see the
system is still doing something!
If you get an "Insufficient memory" message here, it will be followed
by:
Continuing without help file...
As the TNC Help file is optional anyway, paKet will continue with
normal communications although you will not be able to view the TNC
Help file.
E. Log file now closed because of file error
Further input held with <ScrollLock>
A disk error has occurred while writing to the Log File.
Perhaps the most likely cause is the disk has run out of space. You
can delete any unwanted files from paKet's online Disk Directory
Window (<Alt-D>) ; or you can exit to DOS with the <F9> key and fix
the problem there.
If you were logging to diskette, you can replace that diskette and
open another log file on a new diskette.
In most cases paKet will automatically switch on <ScrollLock> to hold
any input data in the buffer until you get the log file going again.
This way you will not lose anything from the log file. When you have
rectified the problem, press <F2> to activate the Log file again (if
you want to) then press <ScrollLock> to release the data from the
Input Buffer.
W. Looks like a Disconnect?
REMOTE mode cancelled.
paKet has detected what looks like a Disconnected message.
If the other station disconnects we must shut down REMOTE mode because
if we are going to send the Menu, we must have someone to sent it to!
Page 106
M to P
E. Maximum 250 lines per 'page'
When displaying the Online Manual or the TNC Help file, each "chapter
or section" is retained in memory for quick and easy scrolling. In
doing this I have imposed a limit of 250 lines for each chapter or
section.
This has proven to be quite ample and works fine with the files as
distributed. So if this message appears, the file is either corrupted
or has been changed by someone (and, come to think of it, isn't that
the same thing?).
I. Message file closed by Disconnect
A "Disconnect" message was detected while paKet is receiving a PMS
message.
The Disconnect is processed and the Message File is closed to preserve
whatever part of the message has been received so far.
E. Must be .......
When making changes to paKet's Online Configuration, there are some
checks performed to ensure the new values entered are valid. paKet
will issue a message in the above format to advise you if it thinks an
error has been made.
W. No, the TNC thinks we are NOT connected!
After pressing <Alt-V> to verify the connected status, this message
will appear if paKet thought there was a connection in the current
window but the TNC disagrees, indicating there is NO connection.
The Communications Window Header is changed to show "Not Connected".
E. No messages available
This message will appear in response to a PMS List request if there
are no messages currently recorded.
E. No such file or directory
This error message occurs after an attempt to Rename or to Move a file
with the <Alt-R> key.
It would usually appear if you have specified a new sub directory in
an attempt to move a file to another subdirectory, but the specified
subdirectory does not exist on this drive.
Page 107
E. Not enough free memory
The external program you are trying to run will not fit into whatever
memory is still available after paKet has taken what it needs.
You might have to return to paKet and exit (<Alt-X>) before trying the
other program again.
W. Not found
If you have initiated a search through the Flashback buffer for some
text (via the <Alt-F> or the <Alt-L> keys) the matching text will be
highlighted. This message will appear if there is no (more) matching
data in the buffer.
E. Now I can't read the PMS DataBase file!
An error has occurred trying to do some housekeeping on the PMS
DataBase file.
As far as the rest of the paKet processing is concerned, this is not a
critical error because normal communications can continue without the
PMS. So normal processing continues. It is likely you will lose the
messages that were in the PMS but check it out.
W. paKet-Protocol Recovery denied
This does NOT look like the same file
We are receiving a Binary File from another station and our system had
requested a paKet Protocol Recovery.
This message appears if the other station has refused our request for
a Recovery because it does not appear to be the same file. The file
already on our system will be preserved and a new file will be
transfered in its entirety.
W. paKet-Protocol Recovery approved
Issuing approval to the receiver station...
We are sending a Binary File and the other station has requested a
Recovery of a partly completed file transfer.
After checking the details provided by the other station, paKet has
decided it DOES look like the same file and is sending its approval to
the other station. Now both sides can begin the transfer from the
agreed point in the file.
W. paKet-Protocol Recovery denied. The receiver's file does NOT match ours.
The entire file will be sent from the beginning
We are sending a Binary File and the other station has requested a
Recovery of a partly completed file transfer.
Page 108
After checking the details provided by the other station, paKet has
decided it is NOT the same file and is sending a message to the other
station, refusing the Recovery request.
W. paKet-Protocol Recovery approved
now appending to file...
We are receiving a Binary File from another station and our system had
requested a paKet Protocol Recovery.
This message will appear if the Recovery is approved by the other
station. The transfer will continue from the point where it aborted
last time. It will be approved provided the other station is using
paKet Protocol and both stations agree it seems to be the same file.
W. paKet-Protocol Recovery requested by the receiver
Attempting recovery - verifying file contents...
We are sending a Binary File to another station and that station
thinks we may have tried this one before, unsuccessfully, because a
shorter version of the same file already exists on that system.
Some details of that file have been provided by the other station and
paKet is now checking to see if it could be the same file.
I. Performing AUTOEXEC.SCP
I. Performing AUTOEND.SCP
The AUTOEXEC and AUTOEND Script files are optional.
If the AUTOEXEC.SCP file is present paKet will run that Script as soon
as it starts up (immediately after any Begin-Auto commands). The
Begin-Auto commands, which may be specified in the Configuration, are
a simpler way to send any initialisation commands to the TNC but a
Script provides more flexibility should the need arise. You can have
both the Begin-Auto commands and the AUTOEXEC.SCP if you wish.
When you press <Alt-X> to exit the program, paKet will look for the
AUTOEND.SCP file and if present, it will run that Script before any
End-Auto commands that may exist in the Configuration.
E. Please close the log file first
You should not edit a file that is already open and being used for
something else. DOS gets horribly confused and upset.
You will get this message if you try to edit the current Log File. If
you really want to edit this Log file, press <F2> to close it first,
then try the Edit command again.
Page 109
E. Please enter a Message Number with the command.
Eg: R 4
In paKet's PMS, the messages are identified by a number. When you
enter a command to process a message, the system needs to know which
message you are referring to.
Reenter the command, specifying the message number after the command
as shown in the above example.
W. Please take care with this. RESTART is the command mostly used.
On most TNCs, RESET will clear everything including your MYCALL!
This message will appear as a warning when you select the Serial Port
Configuration and change the item specifying the command to
initialise your TNC.
When changing Serial Port parameters, you will usually be changing
both the TNC's parameters and the computer's parameters and need to
keep the two devices synchronised in order to maintain communications.
The way this is done is to send the commands to the TNC first because
most TNCs will accept the changes but will not actually apply those
changes until the TNC is re-initialised. Next, you change the
Computer's Serial Port parameters. paKet will then ask you if you
would like to initialise the TNC and (if you reply 'Y') will send the
RESTART command to the TNC.
This works fine until I found the Kantronics range of TNCs are
different to the others and require the RESET command instead of the
RESTART command! So, in order to offer some support for these devices
I added a configurable option to use either RESTART or RESET.
This warning message appears whenever you select RESET because this
command should be selected ONLY if you have a Kantronics TNC! On all
other TNCs I know of, the RESET command will clear EVERYTHING from
it's memory including your callsign! You will have to enter all your
settings again if you (or the program) send a RESET command to the
TNC!
D. Press any key to return to paKet...
This message will appear briefly after an external program has been
run. For example if you run a DOS command from the paKet screen (refer
<F9> key) or Display (<Alt-D>) a file, you will often need to look at
that screen before returning to normal communications.
I. Pressing <F6> again will close the file
This message will appear after you begin an ASCII Text File Receive
operation with the <F6> key. It serves to remind you how to terminate
the file transfer if the other station does not do so.
All data received into this Communications Window will be written to
the selected file until the other station sends a <Ctrl-Z> to close
the file and terminate the File Transfer operation.
Page 110
If the other station does not sent the <Ctrl-Z>, or if you wish to
close the file part way through, you can press <F6> at any time and
the file will be closed and the File Transfer terminated.
C. Printer is not ready!
The Printer status indicates it is not ready to accept any print data.
When the printer is ready, press <Enter> and paKet will continue.
If the Printer Log is already active, you may see some additional
message text:
"Esc to switch off Printing"
In this case you could press <Esc> to clear this message and to switch
off the Printer Log (same as pressing <Alt-P> again).
Page 111
R to S
I. Receive file now closed
An EOF was received while receiving ASCII file
Normal condition - no action required.
D. Receiving Binary file FROM BayCom
Enter the file name in the BayCom system:
When you request a Binary File transfer from a BayCom system, paket
needs to know details of the file so it can generate the required
commands to send to that system. If this command is used with Digicom
(some versions), that system's name for the file may be one containing
blanks or other oddities incompatible with a MS-DOS filename.
If the BayCom system has the desired file in another directory you
should also specify its sub directory name. For example if the file
you want is called MYPROG.EXE and it is stored in the BayCom system's
PRG directory, you would enter:
PRG\MYPROG.EXE
If it responds with a "file not found" error message, check the
directory details with the BayCom operator. A common cause of this
error would be if you inadvertently specify a leading "\", eg:
\PRG\MYPROG.EXE
This message will then be followed by:
What should I call it here?
paKet wants to know what name to give the file here on our system.
You might normally use the same name as that in the BayCom system,
but you can change it if you wish.
And finally, the following message appears to ask for the file size:
Now please enter file SIZE in bytes (-1 for Digicom):
You should enter the size of the file you are transferring because
the BayCom system may not tell us when the transfer is complete.
The BayCom operator should be able to tell you the file size.
If you do not know the file size in BYTES, enter 0 (zero).
If you are trasnferring a file from a Digicom, enter -1 for the
file size to tell paKet it is a Digicom transfer. You will still
have to close th file manually.
I. REMOTE deactivated by Disconnect
The usual way to log off from REMOTE is to enter B for Bye or T for
Talk. This message indicates the connection has been severed by a
Disconnect command to the TNC at either end.
No harm done and no action is required.
Page 112
E. REMOTE is available only while Connected
You have pressed <F3> to place paKet into REMOTE mode and to issue the
menu to the other station, but paKet thinks we are currently not
connected, so there is no other station to send the Menu to!
Try it again after a connection is established.
Occasionally paKet might fail to detect the connection and although
you are really connected to another station, paKet shows "Not
Connected" in the Communications Window Header Line.
If this has happened you will not be able to enter REMOTE mode. You
can correct this by pressing <Alt-V> to ask paKet to verify the
connected status with the TNC. If this changes paKet from "Not
Connected" to show a callsign in the Communications Window Header, you
can then try the <F3> again.
I. Returning to normal communications...
You pressed B (Bye) after using the Sysop PMS Menu. This will release
the <ScrollLock> condition and the system reverts to normal
communications mode once again.
This message informs you of the system's status.
I. Saving configuration parameters in PAKET.CFG
If you make any changes to paKet's Configuration, the changes are
automatically saved to disk.
This message confirms the action taking place.
E. Script file not found
After starting Script Processing with the <Alt-S> key, you have
entered a Script file name, but paKet cannot find that file.
Usually you would select a Script from the Directory Window so this
message would be rare. However, if you have manually entered the file
name, check the spelling and ensure you have entered any subdirectory
details if necessary.
E. Script label not found
A Script command specifies a Script label but paKet cannot find that
label in this Script.
Refer to the Script Processing section of this Manual for details of
Script syntax.
Page 113
E. Script Processing Aborted
If paKet detects a serious problem in your Script file, the Script
will be aborted and paKet returns to normal communications mode.
This message alerts you to the fact that the Script has NOT been
executed.
D. Sending Binary file TO BayCom
Enter the file name in the BayCom system:
When you request the transfer of a binary file to a BayCom system,
paKet will ask for the name you want to give this file when it is
written to the BayCom system. (You can send to some Digicom versions
also).
Usually it would be the same as the file name in our system but you
can change it if you wish.
Another reason for this message is to allow you to specify a
sub-directory as well as a file name for the BayCom system. For
example, say we are sending the file UTIL.EXE to a BayCom system and
we want to write it to the BayCom user's PROG sub directory. So, in
response to the above message you would enter:
PROG\UTIL.EXE
Of course paKet does not know what sub directories are available on
the BayCom system - that is your job to find out.
E. Someone else is connected to another stream.
I cannot (yet?) handle multiple REMOTE operations.
This error message:
a. appears in a popup Message Window if you have pressed <F3> to put
paKet into REMOTE mode when there is more than one station
currently connected.
Try it again later when you have only one station connected.
b. will be sent to another station if that station sends the REMOTE
Trigger in an attempt to activate our REMOTE menu while someone
else is connected on another of our streams.
The REMOTE Trigger will not be processed and the system will
remain in normal communications mode.
D. Sysop PMS menu: <B,H,K,L,R,S,?>
This is the menu that appears when you press <Alt-M>.
The PMS sub system is discussed in its own section of this Manual.
Page 114
D. Sysop PMS Menu Help...
B (Bye) - End Sysop PMS Processing
H (Help) - Display these details
K (Kill) - Kill a message (eg K 3)
L (List) - List available messages
R (Read) - Read a message (eg R 3)
S (Send) - Send a message (eg S (callsign))
? (Help) - Display these details
This list of commands is available only from the Sysop PMS Menu. It
appears in response to the H or ? command.
If it is not self explanatory, I need to make a better help message!
I. System Note at HH:MM:SS - msg
A System Note is an information message that is a little different to
other information messages in that it appears in the Communications
Window (and optionally in the log file) rather than in the popup
Message Window.
These System Notes are mostly used to log information on the success
or otherwise of a file transfer. These file transfer operations can be
time consuming and the operator might start the transfer and go do
something else while the file being transferred. So a brief popup
message might not be seen and it was felt a more permanent record was
required.
Of course no action is required, as this type of message is designed
to cater for those situations where the operator might not be present
anyway.
The HH:MM:SS is the computer's time when the System Note is issued.
"msg" should be self-explanatory. For Example:
"Upload successful - FILENAME.DAT"
Page 115
The...
D. The EOF has not been acknowledged.
We are sending a Binary File with pP or YAPP Protocol and have sent
the last byte followed by the End-of-File code. The other station
should then acknowledge that code so we know the transfer has
successfully completed.
This message appears if the acknowledgement has still not arrived 2
minutes after the EOF code was sent. (2 minutes is the time specified
in the YAPP specifications).
When paKet has sent the last byte and the EOF code, it starts counting
the 2 minute timeout. In most cases 2 minutes is plenty of time for
the other station to get the last of the data and close the file there
before sending its acknowledgement. However, some modern TNCs are
equipped with a large buffer and although paKet has finished sending
the file, your TNC might still have a significant part of it still in
its buffers waiting to be transmitted! And if the TNC buffer is large,
it could easily take more than 2 minutes for the buffer to be cleared.
This message will pop up after 2 minutes to warn you we are still
waiting for the acknowledgement. But, provided paKet is not in REMOTE
mode, the following message will appear:
Would you like to continue waiting for the acknowledgement? (Y/N)
If you do happen to have a TNC with a large buffer, just reply "Y" and
you will get another 2 minutes. The same messages will reappear at the
end of that time if the acknowledgement has still not arrived.
If you reply "N" the transfer will be aborted in accordance with the
original YAPP specifications.
If our paKet system is performing this Binary File transfer in REMOTE
mode, you may not be around to answer the question. In that case the
following message appears:
but as I am in REMOTE mode I will continue waiting...
and paKet will start another 2 minute timeout period. It will do this
3 times (a total of 8 minutes waiting!) before aborting.
W. The message file was not closed
The other station started to send a message to our PMS but has
disconnected without completing the message.
paKet has closed the message file so the message, or at least that
part that we had received, will be retained.
Page 116
E. The other station seems to be in paKet REMOTE mode too.
REMOTE mode cancelled!
The other station has sent what looks like the paKet REMOTE menu while
our system is also in REMOTE mode. They will go on sending the REMOTE
Menu to each other, each time responding with an "Invalid option"
message as the menu is received instead of a valid option!
REMOTE mode is now disabled on this system to avoid the loop and the
unnecessary exchange of error messages.
E. The PMS index is missing so all messages are lost!
E. The PMS data file is missing, so all messages are lost!
Either (or both) these messages could appear if either file used
for the PMS is no longer available.
It is unlikely you have had a hardware problem or some sort of disk
failure because you would have seen a different error message if that
had happened.
This problem is more likely to be due the the files being unavailable
for some reason. Possible reasons include:
1. you have deleted them;
If so, that's tough! You've lost any messages that might have been
in the PMS. If the data file (PAKETPMS.DAT) alone is still there,
you can get a fair idea of the messages by reading it though.
2. the Configuration file has been changed and paKet can no longer
find the files;
In this case, you should change the Configuration by entering
<Alt-Z> then selecting option 8 (File/Directories) to correctly
specify the location of the PMS files.
3. The PMS files are on a diskette and that diskette is not in the
drive.
I don't think you need me to tell you what to do here.
D. The Serial Port has been adjusted.
Would you like me to send a RESTART to the TNC, now? (Y/N)
I assume you have ALREADY set the TNC's parameters.
These messages appear after you make some change to the computer's
serial port via paKet's Online Configuration Window.
Usually when you change one of these parameters, you should change the
setting in the TNC too because if the two devices are not using the
same settings they will not communicate. The trick is to get them
both changed at the same time.
The recommended method is to:
1. send the required commands to the TNC to change the TNC settings;
2. then make the change in paKet's Configuration.
Most TNCs will note the requested change but will not apply certain new
settings until a RESTART command is issued.
Page 117
So, after changing paKet's Configuration, paKet will optionally issue
the RESTART command to the TNC to enable both devices to now continue
with the new settings.
Kantronics TNCs use the RESET command instead of RESTART so paKet has
a configurable option (refer Serial Port options) and will send either
RESTART or RESET depending on the option you choose.
E. The TNC does not appear to be ready
paKet is trying to send a character from a string of data to the TNC,
but the TNC is unwilling to accept it at this time.
paKet will wait up to 20 seconds without complaint, but any longer
than that suggests a possible problem, so this message will appear to
warn you. After this message appears, that character will be sent to
the TNC anyway as in most cases the TNC will have an input buffer of
80 free bytes or more and the character will not be lost.
If the TNC is still locked after another 20 seconds, the next
character will cause the message to be repeated.
This message should appear quite rarely as under normal conditions you
will not fill the TNC's buffers. If you are doing file transfers the
buffers could fill but special handshaking logic in that part of the
program will take care of it under those circumstances. If you have
filled the buffers with lots of KB Macros, then slow down a bit!
If you are using Software Handshaking, paKet will consider the TNC
"not ready" if the TNC has sent an <XOFF> to indicate it cannot accept
any more just yet. paKet will remain in this "not ready" condition
until an <XON> character is received, at which time data will flow
normally once again. However, just in case that <XON> character is
lost or missed for some reason, you can manually reset the "not ready"
condition by pressing <Alt-Q>.
The only action you need to take here is to ensure the TNC and radio
are functioning normally, and slow down if you are pumping in a lot of
data from a Script or Macros.
D. The TNC is not responding.
Abort, Retry, Ignore R
When the program first starts up, it will attempt to establish
communications with the TNC. If it gets no response, this message will
appear to alert you to the possibility the TNC might not be switched
on or the cables might not be properly connected.
There are three options: A, R or I.
A is to ABORT the program and return to DOS. In this case, paKet will
simply give up and you will see the DOS prompt reappear (or the
menu if you started paKet from a menu).
You may decide to take this option if you find something wrong with
the TNC or its connections and prefer to do something else with the
Page 118
computer while you attend to those problems. It is a quick and easy
way out if communications with the TNC cannot be established.
R is the RETRY option. If you can fix the problem that caused this
message to appear, selecting the RETRY option will allow paKet to
continue as if the problem had not occurred. Of course if you have
not really fixed the problem you will get the message again!
I will IGNORE the problem and paKet's processing will continue.
Normally I recommend against the Ignore option when an error
occurs, however in this case it may be desirable to Ignore the
error and allow paKet to continue, despite the lack of
communication with the TNC.
An example of this situation is where the problem is caused by a
mismatch in the Serial Port settings. Either the TNC or the
Computer must be changed to allow normal communications to take
place. It is easier to change the Computer (paKet in this case).
Type "I" to Ignore the errors and when the Initialisation is
complete, you can select the Online Configuration's Serial Port
Window to make the necessary changes. If you do this, don't forget
the TNC's Date/Time may not be set and the usual initialisation
commands may not have been processed by the TNC.
Whenever I get into this situation, I make the necessary changes,
then exit the program so I can make a good, fresh start.
This "Ignore" option will also enable paKet to be used for serial
communications with something OTHER than a TNC! (e.g., a modem)
Page 119
T to U
W. This Connected message is ignored because DCD line is LOW.
(Check the DCDCON option in Configuration/Serial Port window)
A "Connected" message has appeared in the Communications Window but
has been ignored because the DCD line is still low.
paKet uses the Connected message to determine when and to whom we are
connected. Occasionally some text is monitored that looks like a
Connected message and paKet gets confused, thnking there is a new
Connection.
If the DCDCON option is on in the TNC, paKet can check the DCD "light"
to confirm we really ARE connected now.
If a Connected message is detected but the DCD line is still low,
paKet will treat that text as plain data and will display this
message to advise you of the decision taken.
Refer to the discussion on the DCDCON option in Configuration - Serial
Port options and refer to the <Alt-V> key for more discussion on this
issue.
This feature is not used if you are using Software Handshaking.
W. This file already exists.
A new file, (filename), will be created.
When receiving a file, paKet will check to see if the file already
exists and if it does, paKet will issue this warning message.
The original file will not be tampered with; instead paKet will create
a new file, using the same file Name but with a new Extension. It will
try to create a new file with an extension of .000 and if THAT file
exists, it will try .001 etc. When it finds a filename/extension that
does not already exist it will advise you of this filename in the
above message.
For example, if you are about to receive a file "TEXTFILE.DAT" and it
already exists, paKet will create a new file "TEXTFILE.000".
I. This new value will take effect next time you run paKet
After making some changes to paKet's Configuration you may see this
message to remind you that the changes you have made will not take
effect immediately.
There are some things that have to be accomlished at the beginning of
the program, for example the allocation of memory for buffers. So if
you want to change these things, you will have to exit and restart the
program for the changes to become effective.
E. Too many arguments
This message will appear if you have specified an invalid DOS command.
Check the command and reenter.
Page 120
C. Too many connect entries
There are too many entries in the Connect File and the program cannot
hold any more. At the time of writing there is provision for 200
connect entries.
Delete any unwanted entries and if you really need more, you could
establish more than one Connect File, specifying the chosen file name
in the Configuration as required.
E. Too many files
This message will appear if you have selected a function that tries to
display the paKet Directory Window, and paKet finds more than 400
files in this particular directory or subdirectory.
I have reserved space within paKet for handling directories containing
up to 400 files. If you have a directory or sub directory with more
than this number you will not be able to display that directory with
paKet's Directory windows.
I think the limit of 400 files is reasonable as there are certain
inefficiencies in DOS's handling of very large directories.
If you get this message, maybe it is time for a bit of housekeeping?
E. Too many PMS messages here.
I have allowed for a maximum of 200 current messages in your PMS. You
couldn't possibly have that many, surely!
Anyway, paKet can't hold any more so you will have to remove some of
these to make room for any further messages.
E. Too many sections in the Online Manual
This error message means there are more index entries in the
documentation file (the Manual) than I have allowed for.
It is unlikely you will see this message, but if you do it is because
someone has modified the Manual since I released it.
E. Too many Traps in Script.
The Script file you have just loaded contains more than 30 Traps.
Script processing will continue with only the first 30 Traps active
so be warned it may not be doing quite what you want!
Refer to the section on Script Processing for details.
Page 121
W. TRAP in Script ignored.
You must specify 2 fields separated by comma!
The Script file you have just loaded contains a command beginning with
T which suggests a Trap command but the syntax is invalid.
Refer to the section on Script Processing for syntax details.
E. Type ahead buffer is full.
Press <Enter> to send it or <Ctrl-Y> to clear it
The Type Ahead buffer is limited to the number of lines visible on the
screen. So if you have configured a two-line Type Ahead Window, you
have a buffer capacity of two lines.
When this buffer capacity is filled, paKet will not accept any further
characters and you must either type <Enter> to send that buffer to the
TNC or type <Ctrl-Y> to clear the buffer (without sending it).
C. Unknown state in YAPP processing
The YAPP specifications provide for a variety of conditions which the
program must cater for but if there is a problem in the logic at some
stage this message could occur. It is really a program bug so I hope
you never see it!
If you do see this message, the current Binary Transfer will most
likely be unsuccessful. Try it again and if it still fails, you'd
better let me know so I can attend to it. If you could arrange a copy
of the file too that would help with my debugging.
Page 122
W to Z
E. WAIT in Script needs time and a string separated by ,
The Script file you have just loaded contains a command beginning with
W which suggests a Wait command but the syntax is invalid.
Refer to the section on Script Processing for syntax details.
E. We seem to be in Command mode.
REMOTE mode cancelled.
The TNC should not be in Command mode while paKet is in REMOTE mode.
If paKet is in REMOTE Mode it will be issuing the REMOTE Menu. If the
TNC is in Command mode the Menu will not be transmitted to the other
station, but will be taken by the TNC as some sort of "command" and
will be rejected with "What?" or "Eh?" etc.
REMOTE mode is now disabled so you can perform your TNC commands.
When you have finished with the TNC's Command mode, place the TNC back
into CONVERS mode and, if you then want to issue the REMOTE Menu to
the other station, press <F3>.
W. We seem to have lost DCD. REMOTE cancelled.
paKet was in REMOTE mode and the DCD line goes low, indicating the
connection with the other station has been lost.
In normal circumstances paKet detects the "Disconnected" message when
the other station disconnects, and will automatically deactivate
REMOTE mode (if the other station has not logged off normally).
paKet will also monitor the state of the DCD line during REMOTE
operations because if you are using Hardware Handshaking, the DCD line
can be used by the TNC to indicate the other station is still
connected. So, if the DCD line goes low, paKet will disable REMOTE
mode and will issue this message to inform you of the action taken.
This will only occur if you have specified the use of the DCDCON
option in the Configuration - Serial Port options.
D. Which Drive?
This question appears after you select "Change to another drive" from
the Directory Window.
Enter a valid drive letter, it may be either Upper or lower case and
the colon is optional.
E. Without the filesize I wont know when the transfer is finished
You will have to close the file manually (with <Alt-F8>)
You are about to receive a Binary File from a BayCom station (after
pressing <Alt-F8>) but you have entered a file size of zero.
Page 123
This message reminds you it is up to you to close the file when you
think the transfer has finished. It is quite likely the BayCom system
will simply stop sending when the last byte has been transmitted -
there may be no indication from that station that the transfer is
finished.
D. Would you like to continue logging to this file? (Y/N)
After completing the <Alt-W> function to write the contents of the
Flashback buffer to disk, paKet can optionally continue logging to
this same file.
If you answer "Y", the effect is the same as if you press <F2> to open
a Log File and specify that same file as your Log File.
D. Write Flashback buffer to disk
The LOG file is open - add to this LOG file? (Y/N)
If the log file is currently open when you select <Alt-W>, paKet will
give you the opportunity to write the Flashback buffer to the existing
log file so you can keep it all together.
If you wish to do this, reply "Y". If you reply "N", paKet will ask
you for details of the file that is to contain the contents of the
buffer.
E. YAPP command must be YD or YU
This message could appear if you have specified a "Y" command in a
Script but the command is invalid.
Refer to the section on Script Processing for syntax details.
W. You can close the file manually with <Alt-F8> if you wish
When receiving a Binary File from a BayCom system, paKet may not know
when to close the file because the BayCom system may not indicate when
the transfer is complete.
If paKet knows the size of the file, it can close the file after that
number of bytes have been received but sometimes the file size is not
known. In these cases it is up to the operator to close the file
manually by pressing the <Alt-F8> key.
This message pops up to remind you of this option if nothing has been
received from the BayCom system for a while. I figured that if the
other station has stopped sending maybe it has finished? However the
decison is yours and yours alone!
Page 124
PART VI - REMOTE Mode
Overview
Description.
paKet's REMOTE Mode is a facility that allows other users to access and
use our paKet system, even while our system is unattended. A REMOTE
Menu will be issued to the other station and paKet REMOTE will respond
to any of the valid Menu options.
REMOTE Mode would be used mainly for the PMS (Personal Message System)
or for File Transfers, both ASCII text and Binary.
For your protection, the other station will have access only to the
directory or directories you specify. The rest of your system will be
both invisible and inaccessible to the remote operator. You may choose
to disallow all REMOTE operations; or you may disallow just file
Uploads or file Downloads. It is your system - you decide what the
remote operator can see and do. Refer to the section on "Configuration
Windows - REMOTE Mode options" for details on choosing these options.
The operation of REMOTE Mode is somewhat similar to most popular BBS
systems currently available. paKet has a PMS where the other station
can send and receive messages, but it is important to note this is not
a BBS and does not have any Mail Forwarding facilities. Details of the
PMS are covered more fully in its own section in this Manual.
While REMOTE Mode is active, the Status Window displays the word
"REMOTE" to the left of the time display.
Page 125
Activating REMOTE Mode.
REMOTE Mode can only be activated while we are connected to another
station.
There are three ways to put our system into REMOTE Mode:
1. Automatic
You can configure the system to automatically switch into REMOTE
Mode when another station connects to our system.
Details on how to do this are explained in the section on
"Configuration Windows - REMOTE Mode options" in this Manual.
2. REMOTE Trigger
The other station can send the REMOTE Trigger code. This code
too, is configurable although most stations would use the
default which is the <Ctrl-]> (that is Ctrl key with
right-square-bracket or ASCII value 29).
Why such an unusual combination? Well it should be unusual and
unique otherwise we would find paKet switching into REMOTE Mode
unnecessarily! And most of the other codes were already being
used for something or were commonly used as special TNC command
values. <Ctrl-]> seemed to be about the only one left!
It was found in testing that some Commodore 64 systems cannot
send <Ctrl-]>. A DIGICOM user can send that code by pressing
<Ctrl-=>, that is: Ctrl and the "equals" key! If you find some
users cannot manage to send the REMOTE Trigger I suggest the best
solution is to enable the Automatic REMOTE mode so they will get
the REMOTE Menu on connection and will not have to worry about
the Trigger code. For some it is easier to get out of REMOTE Mode
than to get into it!
The Trigger code must be sent as the first and only character on
the line if it is to be recognised by paKet as a REMOTE Trigger.
If you want to specify some other code for the REMOTE Trigger,
refer to the "Configuration Windows - REMOTE options" section of
this Manual for details on how to change it.
If you intend to use this Trigger method to provide access to
your REMOTE system, I suggest you put something into the CTEXT
message to advise the other stations to press <Ctrl-]> (or
whatever) to activate REMOTE Mode. The "Begin" and "End"
auto-commands can be used to alter this message according to
whether paKet is active or not.
3. You can press the <F3> key to switch into REMOTE Mode and send
the first REMOTE Menu to the other station.
Note, while in REMOTE Mode the other station has control of your system
so if you want to talk to that operator or issue some other commands,
you should disable REMOTE Mode first with the <F3> key.
While you are in REMOTE Mode, any of your keystrokes will be taken as
if those characters were RECEIVED from the other station! So if that
operator is having difficulty with some of your REMOTE options, you can
help by typing the correct commands for them!
Page 126
Leaving REMOTE Mode
There are four ways REMOTE Mode can be cancelled:
1. The other station can enter "B", which is the REMOTE Menu command
for "Bye" indicating the user is finished and wants to disconnect.
paKet will:
disable REMOTE Mode;
send "Logged Off" to confirm acceptance of the Bye command;
then issue the Disconnect command to the TNC.
2. The other station can enter "T", which is the REMOTE Menu command
for "Talk" indicating the user no longer wants to use the REMOTE
Menu, preferring to continue this session communicating with us
in normal communications mode.
paKet will:
send a message to the other station accepting the Talk command;
disable REMOTE Mode.
sound the "telephone" bell (if bells are enabled);
If you are not present, the other station can then either
Disconnect the session or send the REMOTE Trigger to get the Menu
back again.
3. You could press <F3> to manually switch the system out of REMOTE
Mode. The effect of this is similar to the other station sending
the "Talk" command.
paKet will send a message to the other station advising them they
are no longer in REMOTE Mode.
4. If the other station Disconnects or if the link between the two
stations fails (which causes a Disconnect in our TNC anyway)
paKet will automatically disable REMOTE Mode as part of the
Disconnect process.
Page 127
The REMOTE Menu - Commands A to L
paKet REMOTE will issue the following Menu to the other station and
will then wait for one of those options to be entered:
paKet (VK2DHU) (A,B,D,H(elp),I,K,L,MD,MU,MW,R,S,T,U,V,W,YD,YU,YW,?) >
The callsign shown will be your callsign as specified in the
Configuration Windows - Miscellaneous options.
The other station must enter one of the these option, otherwise paKet
will issue an "Invalid Option" message.
Menu commands are:
A - Abort a file transfer
This might be used by the other station if an ASCII text file
transfer is in progress and they decide the rest of it is not
required. A quantity of data is already in the TNC's buffer and
will be sent anyway.
B - Bye (logoff)
This option will disable REMOTE Mode and issue a Disconnect
command to our TNC to disconnect the other station.
D - Download an ASCII text file
This operation is a Download from the remote operator's point of
view: an ASCII text file is being sent from our system to the
other station.
The remote operator must send the required filename along with the
"D" command, for example:
D TEXTFILE.DAT
The file will be taken from our Text Send directory (specified in
Configuration Windows - File/Directories) or one of its
subdirectories. If the desired file is in a subdirectory, the
directory path must be specified as well.
I think an example is needed here. Suppose our directory tree
looks something like this and you have specified "C:\PAKET\TEXT\"
as our Text Send Directory.
C:\
├──DOS
├──PAKET
│ ├──BIN
│ │ ├──GAMES
│ │ ├──MISC
│ │ ├──SATS
│ │ ├──UPLOAD
│ │ └──UTILS
│ ├──TEXT < These are the only directories
│ │ ├──BASIC < the Remote operator can see or
│ │ ├──DOCS < access with the D or W commands
│ │ ├──MISC < if C:\PAKET\TEXT\ is specified
│ │ ├──HUMOUR < as our Text Send directory.
│ │ └──UPLOAD <
├──UTILITY
Page 128
Then as far as the Remote operator is concerned, our C:\PAKET\TEXT
directory, and its subdirectories BASIC, DOCS, MISC, HUMOUR and
UPLOAD are available. Our other directories such as DOS and
UTILITY are quite invisible and cannot be accessed.
So, if the file TEXTFILE.DAT exists in our C:\PAKET\TEXT
directory, the remote operator can enter the command:
D TEXTFILE.DAT
and paKet will find (and send) that file.
If the Remote operator wants a file, LAFF.DAT, in our
C:\PAKET\TEXT\HUMOUR\ directory, the following command is
required:
D HUMOUR\LAFF.DAT
An attempt to access another directory will result in an error
message being sent. For example if the Remote operator sent a
command:
D \DOS\README.DAT
paKet would innocently reply that it can't find that file, even if
that README.DAT file DID exist in our DOS directory!
If you do not want another station to transfer any of our files
you can disable this option - refer to "Configuration Windows -
REMOTE options" for details. The option would still appear in the
Menu but the remote operator would get an error message if that
option were selected.
H - Help
? - Help
The contents of the "REMOTE.HLP" file will be sent to the other
station if either of these commands are sent by the remote
operator.
This file must be available in the "current directory", that is
the directory DOS was using when you started the paKet program.
A sample REMOTE.HLP file is supplied with paKet. This file is
plain ASCII text so you can change it to suit your own system. For
example if you do not wish to allow File Uploads, you might like
to remove that detail from your copy of the Help file.
I - Information about this system
The contents of the "REMOTE.INF" file will be sent to the other
station.
This file must be available in the "current directory", that is
the directory DOS was using when you started the paKet program.
A sample REMOTE.INF file is supplied with paKet. This file is
plain ASCII text so you can change it to suit your own
circumstances. For example you might like to add some details of
your computer system, your TNC, your QTH, or any special interests
you have.
Page 129
K - Kill a message from paKet's PMS system
The remote operator may remove any message sent BY that station or
addressed TO that station.
The messages are identified by number so the command must include
the message number that is to be removed, eg: K 5.
If possible, paKet will delete that message from the PMS Database
and will advise the remote operator of the result of this
operation.
Refer to the discussion on the PMS system in its own section of
this Manual for more details.
L - List available messages in paKet's PMS Database
Upon receipt of this command paKet will send a complete listing of
all messages currently stored in our PMS Database, showing one
message per line.
Although all messages are listed here, the remote operator can
access only those messages sent by or addressed to that station,
or messages addressed to ALL.
Refer to the discussion on the PMS system in its own section of
this Manual for more details.
Page 130
The REMOTE Menu - Commands MD to MW (BayCom commands)
MD - Download a Binary file to a BayCom system
This operation is a Download from the remote operator's point of
view: a binary file is being sent from our system to the other
station which presumably is using BayCom.
The remote operator must send the required filename along with the
"MD" command, for example:
MD PROGRAM.EXE.
The file will be taken from our Binary Send directory (specified
in Configuration Windows - File/Directories) or one of its sub
directories. If the desired file is in a subdirectory, the
directory path must be specified as well.
For example, if you refer to the sample Directory Tree shown under
the REMOTE D (Download) command above, suppose you have specified
C:\PAKET\BIN\ as our Binary Send Directory and the required file
is USEFUL.COM in our C:\PAKET\BIN\UTILS sub directory. The
command required from the remote operator would be:
MD UTILS\USEFUL.COM
Of course, if the file is in the C:\PAKET\BIN\ directory, only the
filename would be required.
If you were not in REMOTE Mode and were performing this transfer
via the <F7> key, paKet would ask which filename and directory
should be used on the BayCom system. But as this operation is
actually being performed by the remote BayCom operator, paKet
won't ask that question, leaving the BayCom operator to make his
own decisions.
paKet will:
set up the necessary parameters in the TNC;
display the Binary File Transfer Window;
send the //WPRG command to the BayCom system
send the file
send the //WPRG OFF command to the BayCom system.
Refer to the section on the Binary File Transfer Window for
details of the display and also refer to the "Keyboard Commands"
section of this Manual, where the discussion on the <Alt-F7> key
provides some more detail on sending a Binary File to a BayCom
system.
When the transfer is complete, paKet will return to REMOTE Mode
and the Menu will be reissued to the other station.
If you do not want another station to transfer any of our files
you can disable this option - refer to "Configuration Windows -
REMOTE options" for details.
Page 131
MU - Upload a binary file from a BayCom system
This operation is an Upload from the remote operator's point of
view: a Binary File is being sent to our system from the other
station which presumably is a BayCom system.
That file will be stored in our Binary Recv directory (specified
in Configuration Windows - File/Directories). For your protection,
paKet will not allow the remote operator to specify a drive or
directory.
The remote operator must provide the filename and filesize along
with the "MU" command, for example:
MU PROGRAM.EXE,54257
We need the filesize because the BayCom system does not tell us
when the file transfer has finished. If the filesize is known
paKet can count the bytes received and close the file when they
have all been received.
If the filesize is not known, a 0 may be entered to allow the
transfer to continue but the file will have to be closed manually.
The BayCom operator can do this by entering the BayCom end-of-file
string: <CR>//WPRG OFF<CR>. (The end-of-file string must be entered
exactly as specified otherwise it will not be recognised as the
end-of-file string and will be added to the file!) If that
string is not entered, paKet will close the file after 2 minutes
of inactivity. If present, you can close the file yourself with
the <Alt-F8> key.
It would be much better if the BayCom operator can specify the
filesize!
When the required information has been entered, paKet will:
set up the necessary parameters in the TNC;
display the Binary File Transfer Window;
send the BayCom //RPRG command;
begin the transfer;
Refer to the discussion on BayCom Binary File Transfers under
<Alt-F8> in the "Keyboard Commands" section in this Manual for
more details.
When paKet determines the transfer is complete, the file is closed
and the REMOTE Menu is reissued to the other station.
If you do not want another station to send any files to our
system, you can disable this Upload option - refer to
"Configuration Windows - REMOTE options" for details.
Page 132
MW - What files are available in the Binary Send Directory
If the remote operator sends a "MW" command, paKet REMOTE will
send a sorted list of filenames found in our Binary Send
directory, including the directory names of any subdirectories
found in that Binary Send directory.
If a list of files in one of those Binary Send subdirectories is
required, the REMOTE operator may add that directory name to the
MW Command. Eg:
MW UTILS
Processing for the MW command is identical to that for the YW
command so refer to that command below for details. The REMOTE
operator could enter the YW command to get an identical response.
However, the BayCom user has Upload (MU) and Download (MD)
commands so this MW command is provided for consistency.
Page 133
The REMOTE Menu - Commands R to W
R - Read a message from paKet's PMS
The remote operator wants to read a message that is stored in our
PMS Database.
The messages are identified by number so the command must include
the message number, eg: R 4.
The remote operator may read any message sent BY that station,
addressed TO that station, or to ALL. So, provided that station is
allowed access, paKet will send the contents of the specified
message.
Refer to the discussion on the PMS system in its own section of
this Manual for more details.
S - Send a message to paKet's PMS system
The remote operator wants to send a message, either to you or to
another station. A message addressed to ALL is as close as we get
to allowing Bulletins in this system.
Actually the message is not sent anywhere - it stays here and is
recorded in our PMS Database. However, most other PMS systems use
this same syntax to "Send" a message, so I have conformed and used
the same style for storing a message in paKet's PMS.
If a callsign is provided on the command line, eg: S VK2DHU the
PMS will record the message as being addressed to that station but
if no callsign is given, paKet will assume the message is to be
addressed to you. Your callsign will be that specified in the
Configuration Windows - Miscellaneous options.
The message will be recorded as FROM the Remote operator's
callsign which appears in the Communications Header Line while we
are connected.
Refer to the discussion on the PMS system in its own section of
this Manual for more details.
T - Talk to the paKet operator
This option will disable REMOTE Mode, ring the telephone-style
connect bell and return our paKet system to normal communications.
If you are not present, the telephone bell will ring up to 10
times. The remote operator can either send the REMOTE Trigger to
get the Menu back again or simply Disconnect the session.
U - Upload an ASCII text file
This operation is an Upload from the remote operator's point of
view: an ASCII text file is being sent to our system from the
other station.
Page 134
That file will be stored in our Text Recv directory (specified in
Configuration Windows - File/Directories). For your protection,
paKet will not allow the remote operator to specify a drive or
directory. On my system I use a sub directory called UPLOAD and
anything that is sent to me will appear in that directory. Of
course you may use any directory name you wish, including the Root
directory if that's what you want.
The remote operator must provide the filename along with the "U"
command, for example:
U TEXTFILE.DAT.
This file will be closed when paKet receives a <Ctrl-Z>.
If you do not want another station to send any files to our
system, you can disable this Upload option - refer to
"Configuration Windows - REMOTE options" for details.
V - Version number of this system
When this option is specified, paKet will send the version number
of this paKet program.
It may be useful for the remote operator to know which version we
are currently using as some versions of the program might behave
differently.
W - What ASCII text files are available
If the remote operator sends a "W" command, paKet REMOTE will send
a sorted list of filenames found in our Text Send directory,
including the directory names of any subdirectories found in that
Text Send directory.
The available space on that drive will be sent. If our Text Send
and Text Recv directories are on different drives, the available
space on the Text Recv drive will also be sent. This allows the
other operator to see how much space is available before uploading
a file to our system.
If the remote operator wants to see a directory listing of one of
the subdirectories, the desired directory name must be entered
with the W command. For example, using the sample directory tree
shown in the REMOTE D (Download) command above, suppose the remote
operator wanted a listing of our BASIC directory, the following
command would be required:
W BASIC
Refer to the REMOTE D (Download) command above for a full
discussion on the use of subdirectories.
Page 135
The REMOTE Menu - Commands YD to YW (YAPP or pP Commands)
YD - Download a Binary file using pP or YAPP protocol
This operation is a Download from the remote operator's point of
view: a Binary File is being sent from our system to the other
station using either pP (paKet Protocol) or YAPP protocol.
The remote operator must send the required filename along with the
"YD" command, for example:
YD PROGRAM.EXE.
The file will be taken from our Binary Send directory (specified
in Configuration Windows - File/Directories) or one of its sub
directories. If the desired file is in one of our sub directories,
the directory path must be specified as well. "Wildcards" or
multiple file specifications (eg: *.EXE) may be used to cause
downloading of more than one file in the same transaction,
provided the remote station also supports this feature. Of course
if that remote station is also running paKet, it is supported.
For example, if you refer to the sample Directory Tree shown under
the REMOTE D (Download) command above, suppose you have specified
C:\PAKET\BIN\ as our Binary Send Directory and the required file
is USEFUL.COM in our C:\PAKET\BIN\ directory. The command required
from the remote operator is:
YD USEFUL.COM
If that file was in our UTILS sub directory, the command required
from the remote operator would be:
YD UTILS\USEFUL.COM
paKet will:
set up the necessary parameters in the TNC;
display the Binary File Transfer Window;
synchronise with the other station; then
begin the transfer(s).
Refer to the section on the Binary File Transfer Window for
details of the display and also refer to the "Keyboard Commands"
section of this manual, where the discussion on the <F7> key
provides some more information on sending a Binary File.
When the transfer is complete, paKet will return to REMOTE Mode
and the Menu will be reissued to the other station.
If you do not want another station to transfer any of your files
you can disable this option - refer to "Configuration Windows -
REMOTE options" for details.
YU - Upload a binary file using pP or YAPP protocol
This operation is an Upload from the remote operator's point of
view: a binary file is being sent to our system from the other
station using either pP (paKet Protocol) or YAPP protocol.
That file will be stored in our Binary Recv directory (specified
in Configuration Windows - File/Directories). For your protection,
paKet will not allow the remote operator to specify a drive or
directory.
Page 136
It is not necessary for the remote operator to enter the filename
with the YU command because that information is included in the
Protocol Header.
paKet will:
set up the necessary parameters in the TNC;
display the Binary File Transfer Window;
synchronise with the other station; then
begin the transfer.
When the transfer is complete, paKet will return to REMOTE Mode
and the Menu will be reissued to the other station.
Refer to the section on the Binary File Transfer Window for
details of the display and also refer to the "Keyboard Commands"
section of this Manual, where the discussion on the <F8> key
provides some more detail on receiving a Binary File.
If you do not want another station to transfer any files to this
system you can disable this option. Refer to "Configuration
Windows - REMOTE options" for details.
YW - What files are available in the Binary Send Directory
If the remote operator sends a "YW" command, paKet REMOTE will
send a sorted list of filenames found in our Binary Send
directory, including the directory names of any sub directories
found in that Binary Send directory.
The available space on that drive will be sent. If our Binary Send
and Binary Recv directories are on different drives, the available
space on the Binary Recv drive will also be sent.
If the remote operator wants to see a directory listing of one of
the sub directories, the desired directory name must be entered
with the YW command. For example, using the sample directory tree
shown in the REMOTE D (Download) command above, and assuming you
have specified C:\PAKET\BIN\ as the Binary Send Directory, suppose
the remote operator wanted a listing of our GAMES directory. The
following command would be required:
YW GAMES
Refer to the REMOTE D command for a full discussion on the use of
sub directories.
Page 137
Messages (A to L)
This is a list of messages sent by the paKet REMOTE system to the other
station. They are listed in alphabetic order.
999,999 bytes free
(The upload directory is on another drive - 999,999 bytes free there)
Another station is using our REMOTE mode and has requested a directory
display from our system. The directory that will be shown is the
Download directory, i.e. the directory of files that may be
transferred FROM our system.
When the file details are sent, the first of these two messages will
be added to show the other station how much free space we currently
have on the drive.
If the drive specified for our Upload directory (i.e. the drive used
for files transferred TO our system) happens to be a different drive,
the second of these messages is also sent.
A disk error has occurred here.
This message is a general catch all for various types of file errors
that occur during some REMOTE mode operation. The message will be sent
to the other station when/if such a condition occurs. It will usually
be accompanied by other messages to better define the nature of the
problem, so be guided by the other messages for a course of action.
BaycoM command must be MW, MD or MU.
Another station is using our REMOTE mode and entered a command
beginning with "M" but the command we received is not one of the valid
BayCom commands.
That command is rejected and the above message is returned to the
other station.
File display not available. Sorry.
A station is using our REMOTE mode and has requested a directory
display from our system, but we are unable to prepare the list to send.
When a directory listing is requested, paKet will go through the
following steps:
1. read the requested directory into memory;
2. sort it into alphabetic sequence (by name);
3. write all that to a temporary file;
4. send that temporary file to the other station;
5. delete the temporary file when it has been sent.
If something trips up in any of these steps, the display will not be
available. Typically the cause of such a problem would be related to a
lack on memory to perform the load and sort operations, or a lack of
disk space to create the temporary file.
Page 138
When this message is returned to the other station, the REMOTE Menu
should be issued again and processing continues normally.
File path is ignored (I will use the file NAME).
Another station is using our REMOTE mode and has attempted to send a
file to our system, but has specified a Drive and/or Directory in
addition to the file name.
I have decided to restrict uploads to our system to a single directory
so it is clear to you what may have been uploaded in your absence and
to contain the possibility of a virus-ridden program being loaded into
a working directory.
The above message is issued to the other station for information but
the file transfer will continue. The file will be loaded into the
directory you have specified in your Configuration.
I can't create a new PMS DataBase!
I'll try again next time.
paKet was attempting to perform some housekeeping on the PMS database,
removing any deleted messages to conserve space on the disk. However,
it is unable to create a new copy of the database file. The cause
could be something as simple as a lack of disk space.
Housekeeping can wait till next time so it is a non-critical error (as
far as the PMS is concerned anyway).
This message warns you of the error but then processing continues
normally.
I can't read the message file.
Ask (yourname) to investigate the cause
Someone is trying to read a message from our PMS but paKet is unable
to access the database for some reason.
This message gives the bad news to the user.
The PMS file is either missing or corrupted. If it has been corrupted
you might have to delete it (losing any messages that were stored
there) and allow paKet to start afresh next time it is loaded.
I don't handle Bulletins so I'll treat this as a Personal message.
Someone has entered an "SB" command to our PMS.
This is the usual way to enter a Bulletin into a BBS system, but paKet
does not handle Bulletins. It does not perform outward message
forwarding so there is little point in processing Bulletins.
This message will be stored as a personal message but unless it is
addressed to "ALL", no-one else will be able to read it! Of course you
have access to any message in this system, but noone else (other than
the station who sent the message) will be able to read it.
Page 139
I have a disk error and cannot record the message.
Ask (yourname) to investigate the cause.
A disk error has occurred while paKet is attempting to write to the
PMS files.
This message will be sent to the other station who is trying to leave
a message in our PMS. The message has not been stored.
I need the file name and the file size.
Eg: MU PROG.COM,14392
Enter zero for the filesize if you don't know it's size in bytes.
Another station (probably a BayCom user) is using our REMOTE mode and
has attempted to send a Binary file to our system with the MU command
but has not specified the command correctly.
As the BayCom system does not (yet?) have a file transfer protocol to
indicate when the transfer is complete, paKet needs to know when to
close the file. So, if it knows how many bytes are in the file, it
will close the file when the specified number of bytes have been
received.
If the other station has not specified the file size, the MU command
will be rejected with the above message. If that station does not
happen to know the exact size of the file, a zero filesize may be
specified to tell paKet to wait for the file to be closed manually.
*** Invalid option
A station is connected to our REMOTE Menu system but has entered what
looks like an invalid command. The available commands are those
appearing in the REMOTE Menu. Anything else is considered invalid and
will cause this message to be issued.
It is possible to get lots of these all at once if say, a file
transfer has gone out of control and our REMOTE system keeps receiving
parts of the file when we are really expecting to get just a valid
Menu command! To avoid sending too many unwanted "Invalid option"
messages, paKet will shut down the REMOTE processing and will issue
the "REMOTE mode cancelled" message if there are several consecutive
errors.
Leaving the menu...now communicating with (yourname), the paKet operator.
This message is sent to another station, who was using our REMOTE
mode, when you press the <F3> key to switch off REMOTE Mode.
You are now in normal communications mode.
Page 140
Leaving REMOTE mode - returning to Normal Communications.
I'll ring the bell. If no response soon, maybe (yourname) is not around?
Another station was using our REMOTE mode and has entered a "T" (Talk)
command to cancel the REMOTE menu so personal interactive communications
may be conducted.
paKet will now be in normal communications mode.
The "telephone" bell will be sounded to alert you, because it is
possible you are close by but not aware the other station wants to
talk to you. The bell will stop ringing at your first keystroke, but
if you are not present it will stop after 10 rings.
Logged off...
Another station was using our REMOTE system and has now issued the Bye
command to terminate the session.
This message is sent to that other station before paKet issues the
Disconnect command to your TNC.
Page 141
Messages (M to R)
Message 4 Killed
Someone has killed a message from our PMS and this message is issued
to confirm the success of the operation.
Message 4 stored
Someone has just left a message in our PMS. This message is issued by
paKet to confirm the message has been successfully written to disk.
Msg# Size To From Date Time Subject
When paKet displays a List of available messages in our PMS, it will
display the above headings so the user can better identify the various
parts of the information given.
Details of the message format are listed in full in the PMS section of
this Manual.
(No files)
Another station is using our REMOTE Mode and has requested a directory
display with a W, YW or MW command. If paKet finds the requested
directory empty it will return this brief message to the other station.
No further Information available. Sorry.
Another station is using our REMOTE mode and has asked for further
information on our system by entering the "I" command.
paKet provides this information by sending the file REMOTE.INF, but if
that file cannot be found the above message will be sent instead.
No HELP available. Sorry.
Another station is using our REMOTE mode and has asked for Help by
entering "H" or "?".
paKet provides this help by sending the file REMOTE.HLP, but if that
file cannot be found the above message will be sent instead.
Now I can't find that message
Something is badly wrong if you see this message. I haven't seen it
yet, and if YOU do, it means there is a program bug, and I'd really
like to know exactly what you did to make it happen!
Now I can't read the PMS DataBase file!
Something has just happened to the PMS database. We had been using it
but now it is unreadable. This message is most likely caused by a
genuine disk error, so I hope you never see it!
Page 142
OK, send your message...(Ctrl-Z to end)
When someone is leaving a message in our PMS, paKet will ask for the
Subject of the message and then will issue this prompt to let the user
know it is ready to accept the message and to remind that station to
enter the <Ctrl-Z> to terminate the message. (A disconnect will also
terminate the message, but that's real messy, so we won't tell them
about that!)
Please include the filename with the command.
Another station is using our REMOTE mode and has requested a file
transfer from our system, but has not told us which file to transfer.
This message is sent to that other station to ask for the command to
be reentered with the desired filename.
Ready to receive ASCII text file...(Ctrl-Z to end)
Another station is using our REMOTE mode and has commenced an ASCII
text file transfer to our system.
This message is issued to let the other user know we are ready to
receive and to remind them we need the <Ctrl-Z> to close the file.
(If you are present, you could close the file manually by pressing the
<F6> key at any time).
Ready to receive binary file using paKet Protocol...
Ready to receive binary file using YAPP protocol...
Ready to send binary file using paKet Protocol...
Ready to send binary file using YAPP protocol...
Another station is using our REMOTE mode and has commenced a Binary
File Transfer to or from our system.
When paKet is ready to proceed, it will issue one of the above
messages to the other station. The message sent depends on whether you
have enabled paKet Protocol in your Configuration.
There is a full discussion on paKet Protocol in its own section of the
manual but it is fully compatible with the YAPP protocol so don't be
concerned if it says "paKet Protocol" when you are communicating with
a YAPP station. paKet will automatically detect the presence of
another paKet Protocol station and will use the advanced protocol as
appropriate.
Page 143
REMOTE mode cancelled
Another station is connected and was using our REMOTE Menu, but
something has happened (for example, too many "Invalid option"
messages) and paKet has decided to shut down the REMOTE processing
rather than continually flood the frequency with these "Invalid
option" messages.
The other station is informed of this action with the above message.
paKet resumes in normal communications mode.
REMOTE operations disabled, sorry.
Another station has attempted to trigger our REMOTE mode by entering
the character you have configured as the REMOTE Trigger.
However you currently have disabled REMOTE mode so paKet will refuse
the other station's request and will send this message to let them
know the situation here.
Returning to normal communications...
You have access to the PMS via the <Alt-M> (Message) key. When you
press this key, paKet responds with a Sysop PMS Menu to provide access
to various PMS operations. When you are finished with the PMS and have
pressed B (Bye) paKet closes the PMS and issues this message to
confirm that operations are now back to normal communications mode.
Page 144
Messages (S to Z)
Someone else is connected to another stream.
I cannot (yet?) handle multiple REMOTE operations.
This error message:
a. appears in a popup Message Window if you have pressed <F3> to put
paKet into REMOTE mode when there is more than one station
currently connected.
Try it again later when you have only one station connected.
b. will be sent to another station if that station sends the REMOTE
Trigger in an attempt to activate our REMOTE menu while someone
else is connected on another of our streams.
The REMOTE Trigger will not be processed and the system will
remain in normal communications mode.
Someone is already connected and using REMOTE mode.
Please try again later.
This message will be sent to a station who connects to our system at a
time when some other station is already using our REMOTE mode.
In this version of paKet, REMOTE mode processing requires exclusive
use of the system. So, when this message is sent, paKet will issue a
Disconnect command to the TNC.
Sorry, but this station does not accept Uploads
Another station is using our REMOTE mode and has attempted to send a
file to our system.
This message will be sent to that other station if you have specified
in your Configuration that you do not wish to allow REMOTE Uploads.
Sorry, but this station does not allow Downloads
Another station is using our REMOTE mode and has requested a file
transfer from our system.
This message will be sent to that other station if you have specified
in your Configuration that you do not wish to allow REMOTE Downloads.
Subject for msg 4 (max 30 characters)
When a message is entered into our PMS, paket will prompt the user for
the Subject of the message. This "subject" is limited to 30 characters
so it will fit on the line when the user displays a List of the
available messages.
Page 145
That directory is not available. Sorry.
Another station is using our REMOTE mode and has requested a directory
display from our system, but it appears the directory specified is not
one of ours (probably misspelt)!
This message is sent to the other station, followed by the REMOTE Menu
so they can try again.
The YU command is sufficient - there is no need to specify a file name.
Another station is using our REMOTE mode and has commenced a Binary
File Transfer to our system using the YU command, but the other user
has specified a filename on the command line.
Some other YAPP-compatible systems require the filename (as the YAPP
file header is optional and may not necessarily be sent) but paKet
expects to extract the filename from the YAPP protocol header. This
message is issued to let the other user know a few keystrokes could be
saved next time.
This file already exists. Sorry.
This message is sent to another station if that station has attempted
to send a Text file which already exists in our Text Upload directory.
The REMOTE menu will be reissued so that user can try again with a
different filename.
To leave a message for a particular station, enter 'S (callsign)
Note the <space> after the 'S'. Eg: S VK2DHU
Someone has entered a command beginning with S but it is not a valid
Send command. This message is issued to help the user with the
required syntax.
Without the filesize I wont know when the transfer is finished
So, when your system has finished sending the file, type the following:
<CR>//WPRG OFF<CR>
(the <CR> is the Enter key).
When I receive that I'll close the file; then I'll send the Menu again.
The above series of messages is sent to the other station (probably a
BayCom user) when that operator is sending a Binary File to our REMOTE
system (using the MU command) and that user has given us a file size
of zero.
YAPP command must be YW, YD or YU.
Another station is using our REMOTE mode and entered a command
beginning with "Y" but the command we received is not one of the valid
YAPP commands.
That command is rejected and the above message is returned to the
other station.
Page 146
You are already connected to REMOTE.
This message will be sent to the other station if that user sends the
REMOTE Trigger when we are already in REMOTE mode.
No action required and no harm done.
You are not allowed access to that message
Our PMS is a facility for REMOTE users to send (and receive) messages
to you and to third parties. However paKet allows a user to access
only those messages either sent BY or addressed TO that station (or to
ALL). If the REMOTE user tries to access someone else's message, paKet
will refuse the request, returning this warning message.
You have mail waiting in my PMS
Check it out with the List and Read (and Kill) menu commands
This message is sent to another station who has just connected to our
system if paKet finds at least one message addressed to this station
in our PMS.
paKet does not note whether a message has been read, so this reminder
will be sent every time that user connects to us if the message is not
removed from the PMS.
You may specify a DIRECTORY if necessary, but a DRIVE is NOT permitted
Another station is using our REMOTE mode and has requested a file
transfer from our system, but has specified a DRIVE for the requested
file.
This is not permitted so their command is rejected with this message.
You must specify the other station's callsign.
When you are entering a message into the PMS from the Sysop PMS menu
you must enter the callsign of the station the message is intended for.
When another user is connected to our PMS, the callsign is optional
because paKet will simply assume they are sending the message to you
and will insert your callsign into the "To" field of the message.
Page 147
(This page intentionally blank)
Page 148
PART VII - SCRIPT PROCESSING
Overview
paKet includes a simple Script processing facility. The key word there
is "simple".
This facility offers some degree of automation providing a number of
Script commands for flexibility in setting up a wide range of Script
processes. However I must emphasise that because this is a SIMPLE
facility, it is your responsibility to get it right. There is very
little error checking performed but if paKet detects something strange
the Script processing will be aborted.
However, on a more positive note, it could be useful for regular,
routine operations such as logging on to your BBS, reading your mail,
checking the latest bulletins, or a file transfer. A sample Script file
to do some of these things is given below.
It is possible to write a Script with an appropriate delay to allow the
processing to wait until a specified time before continuing. So,
conceivably, before going to bed you could start a Script to (for
example) wait until 2am, logon to the local BBS, download a Binary
File, and log off.
The Script facility should be sufficiently flexible to allow a variety
of operations, given a little imagination. So if you do develop a
"good" Script file of your own, why not spread it around? Broadcast it
to other users (I suggest a Bulletin addressed to PAKET or perhaps to
IBM rather than to ALL would attract the attention of paKet users). I
would appreciate it if you could let me have a copy too.
Running a Script File.
Press <Alt-S> to commence Script Processing.
A Directory Window will appear with the default Script file name
already highlighted. If you decide to enter a file name manually and
you type a file name without an extension, paKet will assume an
extension of ".SCP" so it is recommended you use an extension of .SCP
for all your Script files.
When you select the desired Script file, that file will be loaded and
Script processing will commence. The word "SCRIPT" will be displayed
in the Status Window to the left of the time display while the Script
is running.
When the Script has completed, the indicator in the Status Window will
disappear and you will be returned to normal communications.
Page 149
Script Commands
The following Script commands are valid:
: label No processing is performed on this line.
It is used by the Goto command.
As no processing is performed here, this could also
be used as a comment in your Script file.
"label" may be any length but the total line length
must be less than 80 chars.
AC Close the Download file.
Presumably this will follow the AD command somewhere
in your Script?
If the file is already closed, this command will be
ignored.
AD filename ASCII File download
(Same as <F6> but you must put filename on the
Script command line. (Eg: AD RECVFILE.DAT) Note
that like <F6> if the file already exists, a new one
will be created with a sequential numeric extension
(RECVFILE.000 or RECVFILE.001 etc).
AU filename ASCII file Upload.
Same as <F5> but again you specify the filename in
the Script command line. (Eg: AU SENDFILE.DAT).
B Send a BREAK (or <Ctrl-C>) to the Serial Port.
(Same as <Alt-B> - return to cmd: mode)
C script_file Call another Script.
A Script file is limited to a maximum of 200 lines,
but if you find this limiting your style, you can
set up a number of Scripts and Call them as
required. Yep, paKet even includes Structured
Programming!
There is no practical limit to the number of nested
Scripts you may call. Each of the called Scripts
should "Return" to the calling Script, in which case
processing of THIS Script will continue with the
command following this Call command. Note the
facility for "flags" to return the status of
important events while in the called file.
D time Delay for "time" seconds, or delay until hh:mm.
or "time" may be 1 to 32767 seconds (about 9 hours).
D hh:mm "hh:mm" is a time of day. If this format is used,
paKet will wait until that time occurs before
continuing. Note, this time may be earlier than the
current time, in which case the system will wait
until that time arrives TOMORROW before continuing.
Page 150
E text Echo text to the screen.
This is included mainly as a form of documentation
within the Script. The text is echoed to the screen
as if it was received from the other station, so it
will appear in your log file if it is active.
FC n Flag Clear
FS n Flag Set
FT n Flag Test
There are 10 flags available within the Script
system.
These are Binary flags (i.e either ON or OFF)
numbered 0 through to 9 and may be used by the
Script Programmer (that's YOU).
It was found by a paKet/Script user that there are
times when you need to remember the status of some
condition during the Script process. By setting one
(or more) of the flags you can test the status of
that flag later in the Script and adjust the
processing as required.
For example you might need to note the fact that a
particular string was received from the TNC (using
the "W" command). When that string was received you
could Set a flag with the Flag Set Command,
(eg) "FS 4".
Later during this Script you could check the status
of that flag with the Flag Test command (eg) "FT 4".
If the flag is set, the next Script command is
performed, but if the tested flag is not Set (or
Clear) the next line in the Script is skipped.
G label Goto "label" and continue the Script from there.
(Yeah, yeah I know Goto is unfashionable!)
L Disk Log File On/Off toggle
This uses the default log filename.
P Printer Log On/Off toggle.
Q Quit.
The Script processing is terminated. This would be
used for an aborted exit.
The Return command is a tidier way to exit a Script.
R Return
This command is especially used to return control to
a calling Script. If used in the first level, or
only Script, Script processing is terminated and
control is returned to paKet. Note the facility for
"flags" to return the status of important events
while in the called file.
A Return will be assumed at the end of a Script file.
Page 151
S text Send "text" to the TNC.
If you want to include a Control character such as
<Ctrl-C>, or an <Alt- > key combination such as
<Alt-A>, refer to the Special Key Codes section of
this Manual for the special syntax. Do not enter
quotes unless you want them sent to the TNC.
A Carriage Return is generated automatically when
"text" has been sent. Note, if you do not want the
<CR> to be sent, add a caret ('^') as the last
character of the text. paKet will then NOT generate
the <CR>. (It won't send that final caret either!)
T label,string Trap - Goto 'label' if 'string' is received.
If 'string' is received at any time during this
Script, processing will continue from the nominated
'label'. Note that this happens even if a "Delay"
or "Wait" instruction is in progress.
For example, say your Script includes the following
commands:
T MSG,Message waiting
T DONE,No Messages Available
Then, if the string "Message waiting" is received
from the TNC at any time during the processing of
this Script, paKet will detect the matching Trap
string and will continue processing from the MSG
label.
And if the string "No Messages Available" is
received at any time during the Script, processing
continues from the DONE label.
The Trap remains set even if nested Scripts are
CALLed, so 'label' must be a defined label within
all Scripts if the Trap is to be effective.
If a Trap is no longer required, it may be disabled
by specifying the command without a string. Eg:
T DONE,
(Note the comma is still required here).
Up to 30 Trap strings may be current at any one time.
W time,string Wait up to "time" seconds for "string" to be
received from the TNC.
The received "string" need not start at the
beginning of the line.
If "string" is received within the specified "time"
the next line of the Script file is skipped,
otherwise the next line is executed.
Do not enter quotes in "string" unless you are
expecting them in the received text.
Page 152
X Exit the paKet program.
This should be used with care. It will not only shut
down the Script, it will also shut down the paKet
program and will return to DOS.
YD Commence a Binary File download.
This assumes the other station is now waiting to
send a Binary File to us with either pP or YAPP
protocol.
YU filename Commence a Binary File upload.
This assumes the other station is now waiting to
receive a file with either pP or YAPP protocol.
'filename' must include full path details unless it
is in the current directory.
! dos_command Run a DOS command.
This will load a copy of COMMAND.COM and will pass
'dos_command' to DOS for processing. When that DOS
command/program has finished, processing of the
Script will continue from the next line in the
Script.
The comments I made for the <F9> key and for the
<Alt-E> in the "Keyboard Commands" section of this
Manual apply here too. You will not have the usual
amount of memory available for these DOS commands
because paKet is still running and still occupying a
lot of your precious memory.
Page 153
The Script File syntax.
The rules:-
1. The Script file is plain ASCII text
(graphic characters > $128 allowed).
2. All lines must be less than 80 characters.
3. Each Script file is limited to a maximum of 200 lines.
(Use the CALL command to CALL other Scripts if you need more).
All spaces will be ignored, except for EMBEDDED spaces in "text" (in the
Send command) and "string" (in the Wait command) - LEADING spaces in
"text" and "string" will be ignored. For example:
s YU PROG.EXE
W 10, Ready to Receive with YAPP protocol
g notready
y u prog.exe
is identical to:
SYU PROG.EXE
W10,Ready to Receive with YAPP protocol
GNOTREADY
YUPROG.EXE
You are the "programmer" here so choose a style that suits you best.
Most people would find the latter example more difficult to read. The
careful use of spaces makes for more easily understood programming, which
probably means fewer logic problems in your Scripts.
Other uses for Scripts:
Once you start using this Script facility, you will find the ideas will
just keep coming. Here are just a couple of thoughts to illustrate:
Run a Script file that Traps on the "*** CONNECTED to xxxxxx" message for
each of your favourite operators, sends them a personal greeting like
BayCom or Digicom does, waits if necessary and invokes REMOTE Mode if
appropriate for that particular operator.
Most of the functions of a PMS can be emulated; certainly the "YU", "YD",
"U", "D", "S", but for selected parameters only.
You may wonder how a Directory listing could be sent? It could be
performed by an exit to DOS which performs the directory listing and
"pipes" it to a temporary file which is sent (AU Script command).
What about a MHEARD listing? This could be performed by opening a
Receive file (AD Script command) then issuing the "MHEARD" command and
closing the file (AC command) when the cmd: prompt is received again.
That file would then be Sent (AU Script command) to the other station.
And so on.
Page 154
A Sample Script
A sample Script file.
: A sample paKet Script to download a file using YAPP protocol
g start
: TRYAGAIN
d 1800
: START
b
s
w 10,cmd:
g GIVEUP
s c vk2atm-1
w 60,PBBS>
g TRYAGAIN
l
s rm
w 120,PBBS>
g Disklogoff
l
s yd prog.exe
w 30,Ready to Send with YAPP protocol
g GIVEUP
yd
d 5
s B
R
:Disklogoff
l
: giveup
b
w 10,cmd:
g END
s D
:end
r
Page 155
Discussion on the Sample Script:
The first line is a comment.
paKet does a Goto to the ":START" label, avoiding the half hour delay the
first time around.
A BREAK signal is sent to ensure the TNC is in Command mode, then an
"empty" Send line which simply sends a <CR> in case the TNC is already in
Command Mode.
If the string "cmd:" is not received within 10 seconds, processing
continues from the GIVEUP label where paKet sends another BREAK signal
and a Disconnect command before Returning to normal processing.
If the prompt is received, a Connect to the local BBS (in this case
VK2ATM-1) is attempted.
If the next prompt is not received within 60 seconds, the following line
is executed and processing will Goto TRYAGAIN where paKet will delay for
1800 seconds (half hour) before attempting the logon again.
If the "PBBS>" prompt is received, The Disk Log file is activated with
the "L" command.
paKet then sends "RM" to ask the BBS to display any mail that may be
waiting. If the next BBS prompt is not received within 120 seconds the
Wait will drop into the next line which is a Goto DISKLOGOFF. There the
Disk Log file is toggled off before Disconnecting.
If the "PBBS>" string is received, the "L" command toggles off the Disk
Log file. paKet then sends "YD PROG.EXE" which is the BBS command to
download that Binary File using pP or YAPP protocol; and waits for up to
30 seconds for the BBS acknowledgement that it is ready to send, going to
GIVEUP if the message is not received within that time. If the BBS is
"Ready to Send with YAPP protocol", paKet performs the YD Script command
which puts the program into Binary File transfer mode where the file
transfer takes place. On completion of the file transfer, the Script
delays for 5 seconds to allow both systems to reset parameters etc.
Then it sends "B" (the BBS Bye command) to log off the BBS before
leaving the Script with a Return to normal processing.
Page 156
PART VIII - PERSONAL MESSAGE SYSTEM (PMS)
Overview
paKet's PMS system offers message handling facilities for you and your
REMOTE users.
The operation of this PMS is similar to most other PMS systems with
facilities for users to list available messages, leave a message, read a
message, and delete a message, but the messages here are stored on disk.
There is one major difference between this PERSONAL Message System and
the Bulletin Board Message Systems: the current version of this PMS does
not handle the automatic Outward Forwarding of messages. If a message
is entered on this PMS it stays here until someone removes it. As there
is no Outward Forwarding, there is little point in handling Bulletins,
which are messages to be broadcast to other stations. However, paKet's
PMS does allow a message to be addressed to ALL which means anyone can
read it.
Suitably programmed BBSs can however forward messages INTO the PMS.
Messages in the system are allocated a message-number when they are
entered. This message-number is retained for the life of the message.
paKet's REMOTE Menu provides access to the PMS for other users. You, the
paKet operator, have full control of the PMS via the Sysop PMS Menu
which may be called up with the <Alt-M> key.
Page 157
The Sysop PMS Menu
You have access to the PMS system via the Sysop PMS Menu. This menu
appears in the Communications Window when you press <Alt-M>:
Sysop PMS menu: <B,H,K,L,R,S,?>
The <ScrollLock> will automatically be applied to hold any input from
the TNC while you are using this menu. Please do not "release" it
yourself - it will confuse the PMS processing if you do!
The options in the Sysop PMS Menu are as follows:
B (Bye) - End Sysop PMS Processing
H (Help) - Display these details
K (Kill) - Kill a message (eg K 3)
L (List) - List available messages
R (Read) - Read a message (eg R 3)
S (Send) - Send a message (eg S VK2XYZ)
? (Help) - Display these details
All operations on the PMS are performed in the Communications Window so
it will be logged if the Log File is active at the time. If you wish to
keep a copy of any messages for future reference or further processing,
you could activate the Log File with the <F2> key before Reading the
messages.
The 'H' command and the '?' command do the same thing which is to
display the brief summary of the Sysop PMS Menu commands shown above.
When you have finished with the PMS system, enter the B(ye) command.
<ScrollLock> will be automatically released and you will see the
message:
Returning to normal communications...
The other commands: K, L, R and S are shared with the REMOTE Menu which
is where other users gain access to our PMS. Refer to the section
"Accessing the PMS" below for detailed information on these commands.
Page 158
PMS commands in the REMOTE Menu
It is via the REMOTE Menu that other users have access to our PMS. The
REMOTE menu is discussed more fully in its own section of this Manual;
here we are interested only in those commands relating to the PMS.
The REMOTE Menu commands relating to the PMS system are K, L, R and S.
A remote user may List all messages in our PMS and may Send a message
to any other station. However they may not Read nor Kill any message
that was not sent by or addressed to that station.
(I am not sure why I bothered to restrict Read access, preventing
remote users from reading other messages, because anyone monitoring the
frequency can "read the mail". It's not really private at all!
But I wanted to prevent remote users Killing other peoples' mail so I
applied the restriction to the Read command as well. Why not?)
When another station first connects to our system, paKet will check the
PMS and if there is any mail addressed to that station in the PMS the
following messages will be transmitted:
You have mail waiting in my PMS
Check it out with the List and Read (and Kill) menu commands
paKet does not note whether a message has been read, so this reminder
will be sent every time that user connects to us until the message is
Killed. This is an incentive to encourage "tidy" usage.
The four commands to access the PMS (K, L, R and S) are shared with
the Sysop PMS Menu and are discussed in the following section,
"Accessing the PMS".
Page 159
Accessing the PMS
There are four commands to access the PMS:
K - Kill a message (eg K 3)
L - List available messages
R - Read a message (eg R 3)
S - Send a message (eg S VK2XYZ)
These commands may be issued by a remote user from the REMOTE Menu or
may be issued by you, the paKet operator, from the Sysop PMS Menu.
Processing is very similar for both situations so both are covered in
this section. I will point out any differences as we come to them.
K - Kill a message from paKet's PMS system
(I wish other systems had used the term "Delete" or "Remove"
rather than "Kill", but that is the accepted term for removing a
message so I use "Kill" for the sake of conformity).
A remote operator may Kill only a message sent BY that station or
addressed TO that station, but if you are accessing the PMS
through the Sysop PMS Menu, you have full authority.
The messages are identified by number so the command must include
the message number that is to be killed, eg:
K 5.
If possible, paKet will delete that message from the PMS Database
and will respond with a message such as:
Message 5 Killed
L - List available messages in paKet's PMS Database
Upon receipt of this command paKet will send a complete listing
of all messages currently stored in our PMS Database, showing one
message per line.
All messages in the PMS are listed here, whether the remote
operator has access to the message or not. For example:
Msg# Size To From Date Time Subject
2 381 VK2DHU VK2JAW JAN-19 14:22 Greetings
4 59 ALL VK2DHU JAN-23 16:00 Good News
7 70 VK2BZC VK2KQX JAN-23 19:30 forgot
8 330 VK2KQX VK2DHU JAN-24 12:36 Blackout
9 422 VK2DHU VK2WAC JAN-25 14:37 NVIAA
Msg# is the number allocated by paKet to each message currently
in the system. A message will retain this number until it
is Killed from the PMS database. Whenever the PMS is
completely cleared of messages, paKet will restart its
message numbers from 1.
Size is the number of bytes this message occupies in the PMS
system.
Page 160
To is the callsign of the addressee.
This is a Personal Message System, so it is intended for
personal messages only. Bulletins will not be accepted and
if attempted, it will be converted to a personal message
before being stored in the PMS database. However, a message
may be addressed to "ALL".
A remote user will be able to view only those messages which
match that user's callsign either in the To or the From
field, or a message addressed to ALL.
From is the callsign of the station who issued the message.
Date is the Computer system's date when the message was stored.
Time is the Computer system's time when the message was stored.
Subject is (presumably) a brief summary of the message contents?
This is the text entered by the sender when prompted for the
Subject.
As this is a Personal PMS, I expect the number of messages in the
DataBase will usually be a manageably small number. So this List
command does not have any options to specify which message or
range of messages you want to List. You simply specify the 'L'
command and you get the lot!
If the PMS DataBase is empty, you will get the following message:
No messages available
R - Read a message from the PMS DataBase
The messages are identified by number so the command must include
the message number that is to be read, eg:
R 5.
paKet will access the PMS DataBase and locate the specified
message. If the command came from a remote user, the contents of
the message will be transmitted to the other station as it is
displayed in the Communications Window. If the command came from
the Sysop PMS Menu, the contents of the message are displayed in
the Communications Window without transmission.
If the message number specified does not exist in the PMS
DataBase, paKet will respond with:
I can't find that message!
As mentioned above, a remote operator may Read only messages sent
by or addressed to that station (or to ALL). If an attempt is
made to read another message, paKet will send:
You are not allowed access to that message
Page 161
S - Send a message to the PMS DataBase.
This is the command used to enter a new message into the PMS
DataBase.
It should be noted that the message is not actually "sent"
anywhere. It is recorded in our PMS DataBase and stays there
until it is Killed.
When the command is entered, a callsign may be specified. Eg:
S VK2DHU
For a remote user, the callsign is optional. If specified, the
message will be addressed "To" that station. If the remote user
does not specify a callsign, paKet will address the message to you.
(Your callsign is taken from the Configuration - Miscellaneous
options Window).
If you are "sending" a message from the Sysop PMS Menu, you don't
have a choice - you must enter the S command with the callsign of
the station you wish to address the message to (or ALL).
When the PMS is ready to take the message it will prompt for the
message header. Eg:
Subject for msg 5 (max 30 characters)
The message number shown is allocated by the PMS system. This
message will retain that number until it is Killed from the
system.
The "Subject" is the text that is shown beside each message when
a List is produced.
Then, finally, the following prompt is issued:
OK, send your message...(Ctrl-Z to end)
Any text that is entered after this will be recorded in the PMS
for this message. A <Ctrl-Z> will terminate the message. paKet
then saves the message details in the PMS DataBase and issues the
following confirmation that all is well:
Message 5 stored
Page 162
Messages
This is a list of messages relating to the PMS system. Some of these
messages appear in the Messages section of this Manual and some appear in
the REMOTE Mode section of this Manual. I felt it desirable to gather
them here, despite the duplication, for your convenience.
A disk error has occurred here. Your message is not saved.
A disk error has occurred here - message NOT killed
Either of these messages will be sent if DOS returns an error message
when paKet is trying to update the PMS DataBase.
You should investigate the cause of the error, by performing the usual
checks for disk space, diskette door open, etc. If the operation was
attempted by a remote operator they will have to try again when you
have rectified the problem.
Housekeeping...tidying up the PMS DataBase...
From time to time, when you are using the Sysop PMS Menu (refer the
<Alt-M> key) paKet will perform some internal housekeeping to minimise
any wastage of space in the PMS sub-system. This message appears
briefly to inform you of this housekeeping.
I can't create a new PMS DataBase
I'll try again next time.
paKet was attempting to perform some housekeeping on the PMS database,
removing any deleted messages to conserve space on the disk. However,
it is unable to create a new copy of the database file. The cause could
be something as simple as a lack of disk space.
Housekeeping can wait till next time so it is a non-critical error (as
far as the PMS is concerned anyway).
This message warns you of the error but then processing continues
normally.
I can't find that message!
The PMS command must include the message number but in this case the
number specified does not exist in this PMS.
The command should be entered with the correct message number. A List
command ("L") will reveal the available messages.
I can't read the message file.
Ask (yourname) to investigate the cause
Someone is trying to read a message from our PMS but paKet is unable to
access the database for some reason.
The PMS file is either missing or corrupted. If it has been corrupted
you might have to delete it (losing any messages that were stored
there) and allow paKet to start afresh next time it is loaded.
Page 163
I don't handle Bulletins so I'll treat this as a Personal message.
Someone has entered an "SB" command to our PMS.
This is the usual way to enter a Bulletin into a BBS system, but paKet
does not handle Bulletins. It does not perform message forwarding so
there is little point in processing Bulletins.
This message will be stored as a personal message but unless it is
addressed to "ALL" (or a valid callsign), no-one else will be able to
read it! Of course you have access to any message in this system.
I have a disk error and cannot record the message.
Ask (yourname) to investigate the cause.
A disk error has occurred while paKet is attempting to write to the PMS
files.
This message will be sent to the other station who is trying to leave a
message in our PMS. The message has not been stored.
Message 5 Killed
Someone has killed a message from our PMS and this message is issued to
confirm the success of the operation.
Message 5 stored
Someone has just left a message in our PMS. This message is issued by
paKet to confirm the message has been successfully written to disk.
Msg# Size To From Date Time Subject
This is the header line that is displayed before a List of messages to
help identify the various fields that are displayed.
This header is explained in detail in the section on Accessing the PMS
above.
No messages available
This message will appear in response to a PMS List request if there are
no messages currently recorded.
Now I can't find that message
Something is badly wrong if you see this message. I haven't seen it
yet, and if YOU do, it means there is a program bug, and I'd really
like to know exactly what you did to make it happen!
Page 164
OK, send your message...(Ctrl-Z to end)
When someone is leaving a message in our PMS, paKet will ask for the
Subject of the message and then will issue this prompt to let the user
know it is ready to accept the message and to remind that station to
enter the <Ctrl-Z> to terminate the message.
Please enter a Message Number with the command.
Eg: R 4
In paKet's PMS, the messages are identified by a number. When a PMS
command is entered the system needs to know which message is to be
processed.
The command must be reentered with the message number as shown in the
above example.
Returning to normal communications...
When you are finished with the Sysop PMS Menu and have pressed B (Bye)
paKet closes the PMS and issues this message to confirm that operations
are now back to normal communications mode.
Subject for msg 5? (max 30 characters)
When a message is entered into our PMS, paket will prompt the user for
the Subject of the message. This "subject" is limited to 30 characters
so it will fit on the line when the user displays a List of the
available messages.
Sysop PMS menu: <B,H,K,L,R,S,?>
This is the menu that is displayed when you press <Alt-M>.
Refer to the section on the Sysop PMS Menu above for full discussion.
The PMS index is missing so all messages are lost!
The PMS data file is missing, so all messages are lost!
Either (or both) these messages could appear if either file used
for the PMS is no longer available.
It is unlikely you have had a hardware problem or some sort of disk
failure because you would have seen a different error message if that
had happened.
This problem is more likely to be due the the files being unavailable
for some reason. Possible reasons include:
1. you have deleted them;
If so, that's tough! You've lost any messages that might have been
in the PMS. If the data file (PAKETPMS.DAT) alone is still there,
you can get a fair idea of the messages by reading it though.
Page 165
2. the Configuration file has been changed and paKet can no longer
find the files;
In this case, you should change the Configuration by entering
<Alt-Z> then selecting option 8 (File/Directories) to correctly
specify the location of the PMS files.
3. The PMS files are on a diskette and that diskette is not in the
drive.
I don't think you need me to tell you what to do here.
To leave a message for a particular station, enter 'S VK2XYZ'
Note the <space> after the 'S'. Eg: S VK2XYZ
Someone has entered a command beginning with S but it is not a valid
Send command. This message is issued to help the user with the required
syntax.
Too many PMS messages here.
I have allowed for a maximum of 200 current messages in your PMS. You
couldn't possibly want that many, surely!
Anyway, paKet can't hold any more so you will have to remove some of
these to make room for any further messages.
If the remote operator is using the PMS, the following message will
also be sent:
Ask (yourname) to kill some to make room
If you are using the Sysop PMS Menu, the following message will be
displayed:
Try killing some before trying again.
You are not allowed access to that message
paKet allows a remote user to access only those messages either sent BY
or addressed TO that station or ALL. If the REMOTE user tries to access
someone else's message, paKet will refuse the request, returning this
warning message.
You have mail waiting in my PMS
Check it out with the List and Read (and Kill) menu commands
This message is sent to another station who has just connected to our
system and paKet has found at least one message addressed to this
station in our PMS.
paKet does not note whether a message has been read, so this reminder
will be sent every time that user connects to us if the message is not
removed from the PMS.
You must specify the other station's callsign.
When you are entering a message into the PMS from the Sysop PMS menu
you must enter the callsign of the station the message is intended for.
Page 166
When another user is connected to our PMS, the callsign is optional
because paKet will simply assume they are sending the message to you
and will insert your callsign into the "To" field of the message.
Page 167
(This page intentionally blank)
Page 168
PART IX - CONTEST MODE
Overview
paKet includes a Contest Mode. This has nothing whatever to do with DX
Contest activity, but rather it is a mode designed to monitor the
progress and results of a sporting event such as a Race or Triathlon.
The scenario is one base station running paKet in Contest Mode, and one
or more Checkpoint stations communicating contestant information to the
Base station.
Any normal Packet Radio setup will do, including any standard AX-25 TNC.
If you can run paKet for normal communications, you should be able to run
it in Contest Mode. The Checkpoints need not be running paKet.
paKet's Contest Mode will record times for each contestant at each
Checkpoint. At this stage, the program assumes all contestants started at
the same time for the purpose of calculating placings. The program will
automatically return acknowledgements to Checkpoint operators, either
accepting the data or returning one of many self-explanatory error
messages. The program caters for multiple pass Checkpoints where
contestants may pass a particular Checkpoint more than once.
This is a rather specialised part of paKet and it seems is rarely used. I
was tempted to remove the code and the documentation from this version of
paKet to help contain the ever growing size of the system. However, it
is there and seems to work (and there is a bit of nostalgia too because
this Contest Mode is the very reason paKet was created in the first
place). But I would suggest to anyone contemplating the use of Contest
Mode to contact me (VK2DHU @ VK2ATM.NSW.AUS.OC) before committing
yourself to a particular event. I hope this part of the Manual will
provide sufficient information to get you going but I'd like to know
about your use of the system in this way and maybe I can help too?
In any case, I do recommend you set up a trial "contest" with a few
volunteers to send data as if they were real checkpoints. This way you
will get a feel for the system and can experiment with some of the
commands and features without the pressure that will inevitably occur on
the Big Day.
Page 169
Base Operation
Setting up the Checkpoint File (CKPT.DAT)
A data file CKPT.DAT must be set up before the contest begins. This
data file identifies the valid Checkpoint callsigns. The system will
function regardless of the stream (or channel) each Checkpoint connects
to: once the Checkpoint is connected, paKet remembers which Checkpoint
is on which stream. The format of each CKPT.DAT record is:
Checkpoint-number <space> Checkpoint-callsign
If a Checkpoint radio operator is to process data for more than one
Checkpoint (ie if the course brings the contestants back to this point
so they pass that operator more than once), that callsign will appear
in the file for each contest Checkpoint. For example, in the following
example of the file, an operator with the callsign VK2DHU is to do a
Checkpoint on a circuit where contestants pass three times as
Checkpoints 2, 4 and 6:
1 VK2CZZ
2 VK2DHU
3 VK2ABC
4 VK2DHU
5 VK2ABC
6 VK2DHU
7 VK2ABC
8 VK2XYZ
9 VK2BZC
10 VK3TT
11 VK2XXX
12 VK2YCB
If the CKPT.DAT file is not available the Contest Mode will not
activate!
Starting Contest Mode.
To start the system, run paKet as per normal operating instructions.
Then press <Alt-F2> to enter Contest mode. Three smaller windows appear
in the top half of the display showing:
┌──Checkpoint 3──┐ ┌─Contestant 105─┐ ┌───────Placings───────┐
│ 08:15 105 │ │ 1 06:35 │ │ 1 120 14 16:02 │
│ 08:26 155 │ │ 2 07:50 │ │ 2 356 14 16:34 │
│ 08:35 183 │ │ 3 08:15 │ │ 3 378 14 16:39 │
│ 09:00 295 │ │ 4 09:05 │ │ 4 205 14 16:41 │
│ 09:00 387 │ │ 5 09:57 │ │ 5 375 14 16:41 │
│ 09:05 378 │ │ 6 11:00 │ │ 6 105 14 16:48 │
│ 09:05 194 │ │ 7 12:13 │ │ 7 194 14 16:48 │
│ │ │ 8 12:55 │ │ 8 235 14 17:28 │
└────────────────┘ └───Placed 6───┘ └──────────────────────┘
─── ────────── Window 1 - Stream A - VK2DHU ──────────────────────────
18:59 144
19:14 290 55
19:07 244 142 77 105
19:08 145
Page 170
As data is received, these windows update automatically. So When
Checkpoint number 3 is displayed, any data received from that
Checkpoint will appear in the window. Similarly any times for the
contestant displayed in the second window will appear there immediately
the data is received from the Checkpoints. Placings too, update
automatically with the leading contestants appearing at the top.
The Base operator has the following additional commands available
during Contest Mode operations:
Alt-F4 Reload the Contest Matrix
For performance reasons, the entire array of results are
maintained in memory. So, if a power failure or system failure
occurs, these results are lost.
To provide a recovery mechanism, the Contest Matrix (which
contains the time for each Contestant for each Checkpoint)
will be automatically written to Hard Disk every 10 minutes
and optionally to diskette whenever you choose to press
<Alt-F10>.
So, if a failure has occured, start Contest Mode again when
the system becomes available and press <Alt-F4>. paKet will
ask you for the drive which contains the Matrix. You would
normally specify the hard Disk unless you have taken a more
recent diskette dump with the <Alt-F10> key.
The Matrix is reloaded and Contest Mode processing can
continue from that point. You might need to ask the Checkpoint
operators for some data to be reentered in case they had
entered some times after the last Matrix Dump was taken. If
they enter a time that has already been recorded they will get
a "Duplicated" message, but no harm is done.
Alt-F5 View a Checkpoint
<Alt-F5> will ask which Checkpoint you want to view, then will
display details for that Checkpoint in the Checkpoint Window
at the top left of the screen.
You will see the times and the contestant numbers of those who
passed through the Checkpoint at those times. While viewing
this window you may press <Up-Arrow> or <Down-Arrow> to scroll
the data in the window.
Note the border of this window will flash or change colour to
remind you the system has stopped processing data while you
are viewing the window. So try not to leave it in that state
for too long. (The Checkpoint operators will not be getting
their automatic acknowledgements while you are doing this!).
Press <Esc> when finished, to allow normal data processing to
continue.
Page 171
Alt-F6 View a Contestant
This is a similar function to the previous one, but of course
operates on the second window where you may view the progress
of a particular contestant.
You will see the Checkpoint numbers and the times this
contestant passed through those Checkpoints.
Again, press <Esc> when finished viewing this window.
Alt-F7 View Results
The results are calculated and displayed automatically, but
you cannot see all contestants so this function allows you to
scroll through the entire list of contestants to view the
up-to-date placings.
You will see in the Results Window at the top right of the
screen, the Placing, Contestant number, last Checkpoint passed
and the time at that Checkpoint.
<Esc> returns the system to normal processing.
Alt-F8 Edit Results
There may be occasions where the data recorded is incorrect
and needs to be adjusted. This function allows you, the Base
operator, full control to change any time for any contestant
for any Checkpoint.
Pressing <Alt-F8> brings up the Contestant window with a
highlight bar (after you select the desired Contestant). Move
the highlight bar to the Checkpoint you wish to change; press
<Enter> for "Edit Mode"; then enter a new time (enter 00:00 to
delete it). The system will automatically adjust placings to
reflect the change.
Alt-F9 Print the contest results
This function may be selected at any time, but for a large
contest it is recommended some form of print buffer be used.
Normal processing will stop while the printing is done.
It will not print any Checkpoints that have not yet seen ANY
contestants.
Alt-F10 Dump Contest Matrix
Refer to the <Alt-F4> command above for comments on paKet's
recovery mechanism in case of some failure during the Contest.
paKet will write the Matrix to hard disk automatically every
10 minutes but this <Alt-F10> option is a precaution that
copies the Matrix to another file, preferably on diskette. It
is like backup - should never be required, but...
This may be used at any time during the Contest.
Page 172
Checkpoint Operation
Data is sent by the Checkpoint Operators in the format:
HH:MM nnn nnn nn nnn n nnn
where HH:MM is the time the contestant passed that Checkpoint (the
system will accept a ";" or a ":" character as the time separator). The
rest of the line contains the number of each contestant who passed
through this Checkpoint at this time. Lines must be less than 80
columns, but experience suggests it is better to limit the number of
contestants per line to 5 or 6.
For example:
19:07 244 142 77 105
The system will perform SIMPLE data validation. If the time is not sent
in the correct format, the entire line is assumed to be an invalid data
line, and is treated as a comment to the Base operator. It will cause a
beep to emanate from the Base system to alert that operator there is a
message that possibly requires attention.
A Checkpoint operator at a multi pass Checkpoint is usually too busy to
figure out which pass a contestant is on. So, using the above CKPT.DAT
file as an example: when a line of data is received from VK2DHU the
system will (for each contestant on the line) look to see if any times
have been recorded for the contestant at Checkpoint 2; if not, this
time will be recorded. If Checkpoint 2 has been recorded, it will look
at Checkpoint 4 and if that is empty, the time is taken to be for
Checkpoint 4. Similarly the time will go into Checkpoint 6 if 4 was
recorded. This is how the system caters for the multiple pass
Checkpoints.
For the simpler situations where a radio operator is sending data for a
single Contest Checkpoint, there should not be more than one entry for
a particular contestant. If a second entry is received, the system will
overwrite the previous time with the new time, and will send an
appropriate message back to the Checkpoint operator to tell him/her of
this. Ideally, that operator can then check the paperwork there to see
if maybe a mistake was made and it can be corrected by the Checkpoint
operator with a further transmission as necessary.
If all goes well, the Base operator should have very little to do. The
Checkpoint operators should be able to see the acknowledgements of
their data and they should be able to correct any of their own errors
that show up.
Normal (non-Contest-Data) communications.
The Contest Mode has not had a lot of live testing. There were two
large Triathlons and there has been some local testing, but I am not
entirely confident the code is as good as it could be. Until the system
is fully proven to be sound and reliable, I prefer to keep
non-Contest-data communications to a minimum, maybe use another packet
station at the Base, or use voice communications. The BASE operator
will have to manage many Communications windows simultaneously so an
outstanding message on the Contest system could easily be missed.
However, the system SHOULD allow normal chat mode even while in Contest
Mode. Any non valid data received at the base will cause a beep to
alert the Base operator but will otherwise cause no harm to the results
Page 173
recorded. If a message is to be sent to a Checkpoint I like to precede
my message with an * so the system would be sure to recognise this as a
non-data message.
Logging the Contest activity.
During processing all valid data records; details of all Connects and
Disconnects; and any Edits (refer <Alt-F8> above) are recorded in a
CONTEST.LOG file. This provides a full record of all Contest activity
so may be useful to help resolve any disputes that arise.
However, it is recommended that paKet's normal Disk and printer Log
functions also be used for the duration of the Contest. The hard copy
might prove valuable at the end of the day if there are any queries,
especially if there were some system problems during the day.
Page 174
PART X - TECHNICAL
Hardware vs Software Handshaking.
"Handshaking" is a technical term that refers to a method used to
regulate the flow of data between two devices - in this case between the
Computer and the TNC.
Handshaking is required to prevent loss of data. For example, it is
quite possible to send data to the TNC faster than the radio network can
take it, even at low baud rates. This is OK for a while because the TNC
has a memory buffer and the data will be held there until it can be
transmitted. However, there is a limit to the amount of data that can be
held in the TNC's memory, and if the computer continues to send, some
data will be lost. So, if the TNC's buffer is filling up it will ask the
computer (via its "Handshaking") to stop sending.
The reverse could apply, where the TNC could be sending data to the
computer faster than the computer can process it. If you think about
it, a baud rate of 9600 means there is only one millisecond between
characters! So, at that rate the computer cannot do much processing,
especially the slower computer systems. If the computer program was
unable to process the data quickly enough, it could use "Handshaking" to
ask the TNC to stop sending in order to allow the computer system time
to catch up.
There are two forms of Handshaking, both supported by paKet:
Hardware Handshaking and Software Handshaking.
Hardware Handshaking:
Hardware Handshaking is preferred, although it will work only if you
have the correct cable installed. A "normal" RS-232 cable will have 9
(or more) pins connected, some of which carry data but most of which are
used for various forms of hardware level communication. With this
method, the two devices (the Computer and the TNC) switch some of these
lines on and off to tell the other whether it is OK to send more data.
Should you wish to prepare a cable to use the Hardware Handshaking, the
following table shows the connections required (connections shown for
both a 9 pin and a 25 pin connector):
DE-9 DB-25 Signal Description
1 8 DCD Carrier Detect Needed to enable the CONNECT check
2 3 RXD Receive Data Essential!
3 2 TXD Transmit Data Essential!
4 20 DTR Terminal Ready Optional
5 7 GND Signal Ground Essential!
6 6 DSR Data Set Ready Optional
7 4 RTS Ready to Send Needed for Hardware Handshake
8 5 CTS Clear to Send Needed for Hardware Handshake
9 22 RI Ring Indicator Unnecessary for paKet
So, a cable can be constructed using a length of six-conductor flexible
cable (low-capacitance shielded is desirable but not essential) such as
telephone flex with a plug on the modem end and socket on the computer
end, wired pin-for-pin according to the above table (it may also adapt
from DB-25 to DE-9 connector in the process).
Page 175
If, say, the TNC wants to ask the Computer to stop sending, it will
switch off the CTS signal. The Computer (in this case, paKet) will stop
sending data while the CTS signal is low (or off). When the TNC is able
to accept data once again, it will switch on the CTS line and paKet will
resume sending from where it left off. When this happens you might
notice the CTS "light" in the Status Window come on and off as the two
machines talk to each other.
Check your TNC Manual for any special connection requirements. Most TNCs
do not use the DTR, DSR or RI functions.
Software Handshaking:
Some so-called RS-232 cables have only 3 pins connected: one line for
Receive Data, one for Transmit Data and a Signal Ground. With these
cables, Hardware Handshaking is not possible and you must specify
Software Handshaking.
With this method, the two systems (the Computer and the TNC) must do
their handshaking via special data codes, conventionally known as <XOFF>
and <XON>.
If, say, the TNC wants to ask the Computer to stop sending, it will send
the <XOFF> code to the Computer. When it is able to accept data once
again, it will send an <XON> character. When this happens you might
notice in the Status Window, the words "Software Handshaking" will be
replaced by "XOFF" temporarily, indicating we are waiting for the TNC to
clear its buffers before it can accept some more data.
On a three-wire only cable, RTS and CTS should be connected together on
the TNC plug else the TNC may not talk to you AT ALL!
Setting the chosen Handshaking method in the TNC - XFLOW:
It is important to note that configuring paKet to either Hardware or
Software Handshaking will set up the COMPUTER to use that method, but
the TNC needs to be told too! It may not work unless both devices are
set to use the same method.
The TNC's handshaking is set with its XFLOW command:
for Hardware Handshaking, set XFLOW OFF
for Software Handshaking, set XFLOW ON.
If you encounter problems with File Transfers, my experience is that the
problem is often related to the incorrect setting of XFLOW in the TNC.
With paKet's online configuration facility, it is easy to change from HW
to SW mode and vice versa. To do this without changing XFLOW in the TNC
is to invite problems.
In closing this section, it should be pointed out (in case it is not
already obvious) that if you do happen to have a full cable, you may
choose to use either Hardware or Software Handshaking. If you choose
Software Handshaking, the system will not use the additional
connections. The reverse is not the case, of course. If you do not have
a full cable, you don't have a choice!
Page 176
PREFERRED TNC SETTINGS
This list of TNC settings is not a complete set of commands for your
TNC. It is intended to be a guide to some of the preferred settings for
use with paKet.
There are some differences in some TNC commands - a command may be
available in one TNC and not another. Or, it may be known in other TNCs
by a different name. So, if your TNC does not have a command listed
below, just skip that one.
8BITCONV ON
We do NOT want the top bit stripped from our data. You will see
below we have AWLEN set to 8 so we are using all 8 data bits.
This is especially useful if some graphics characters are being
sent. It does not affect Binary transfers.
AWLEN 8
Use 8 data bits so we can send all characters including graphic
characters. You should also set PARITY to "None".
paKet must be configured to the same value - refer to the
Configuration Windows - Serial Port for details.
CHCALL OFF
This must be OFF so we do not get the callsign of the other
station coming through with a change of stream character. (paKet
remembers the callsigns associated with the different streams).
This, in some TNCs, is the same as the STREAMCA in others.
CHDOUBLE ON
This is optional but STRONGLY RECOMMENDED to be ON.
If ON, you must set the corresponding option ON in paKet's
Configuration Windows - Multi User options.
This, in some TNCs, is the same as the STREAMDBL in others.
If your TNC has neither CHDOUBLE nor STREAMDBL you must set
paKet's Configuration option OFF.
CHSWITCH $7C (|)
You may set this character to any value you wish, although most
users seem to retain the default which is the vertical bar
character ("|").
paKet must be configured to the same character (whatever you
choose) and this is recorded in paKet's Configuration Windows -
Multi User options.
This, in some TNCs, is the same as the STREAMSW in others.
CMDTIME 1 second
Please leave this set to the default of 1 second.
COMMAND $03 (Ctrl-C)
This must be left set to its <Ctrl-C> default setting.
Page 177
CONMODE CONVERSE
The only time paKet must use Transparent Mode is for Binary File
transfers, and paKet will switch automatically. So leave this
set to CONVERSE, otherwise Stream switching will not work
correctly.
DCDCONN ON
If you are using Hardware Handshaking, set this ON.
paKet will work either way, but the Status Display can then
indicate with its DCD "light" whether or not you are currently
"Connected".
If set to ON, it may also be used by the paKet program to
confirm the "Connected" status of the TNC
paKet's Configuration Windows - Serial Port must also be
configured to the same setting chosen for the TNC.
ECHO OFF
paKet does its own echoing, so this should be OFF.
FLOW OFF
paKet has its own Flow Control, so this should be OFF.
INTFACE BBS
Kantronics TNCs have this command. Setting INTFACE to BBS will
ensure we don't get unwanted messages interfering with our
processing.
MCON OFF or 0
You may choose to have this option ON sometimes, however it will
interfere with REMOTE Mode and with Binary File transfers if ON
- the system cannot distinguish the Monitored data from the
Binary data! paKet will turn it off before a Binary File
transfer anyway.
The preferred setting is OFF.
MDIGI OFF
Preferred setting is OFF for the same reason as for MCON.
NEWMODE ON
This could be either way and is a matter of personal preference.
You may like to have NEWMODE OFF if you often work multiple
connections because when one disconnects the TNC will revert to
Command Mode (if NEWMODE ON) and you have to switch it back to
Converse Mode to continue talking to the other station. In that
case you might prefer to set NEWMODE OFF and leave the TNC in
Converse Mode.
NOMODE OFF
Preferred setting is OFF so the TNC will switch to Converse Mode
when you establish a connection.
Page 178
PARITY 0 (none)
This is related to the Word Length (see AWLEN above) and should
be set to "No Parity".
paKet must be configured to the same value - refer to the
Configuration Windows - Serial Port for details.
PASS $16 (Ctrl-V)
SENDPAC $0D (Ctrl-M)
START $11 (Ctrl-Q)
STOP $13 (Ctrl-S)
Please leave all these set to their default values.
STREAMCA OFF
This must be OFF so we do not get the callsign of the other
station coming through with a change of stream character. (paKet
remembers the callsigns associated with the different streams).
This, in some TNCs, is the same as the CHCALL in others.
STREAMEV OFF
paKet does not need the stream id with every packet. This is
required only upon change of stream - to have this on would only
result in the transfer of unnecessary additional data.
STREAMDBL ON
This is optional but STRONGLY RECOMMENDED to be ON.
If ON, you must set the corresponding option ON in paKet's
Configuration Windows - Multi User options.
This, in some TNCs, is the same as the CHDOUBLE in others.
If your TNC has neither STREAMDBL nor CHDOUBLE you must set
paKet's Configuration option OFF.
STREAMSW $7C (|)
You may set this character to any value you wish, although most
users seem to retain the default which is the vertical bar
character ("|").
paKet must be configured to the same character (whatever you
choose) and this is recorded in paKet's Configuration Windows -
Multi User options.
This, in some TNCs, is the same as the CHSWITCH in others.
TRFLOW OFF
TXFLOW OFF
These commands are used for Software Handshaking in Transparent
Mode. You should set them both OFF. paKet will switch them on
and off if required.
Page 179
USERS n
Although not essential, it is considered desirable to set this
parameter to the same number of users as you have Communications
Windows. Then you know you can have a separate window for each
of the possible connections.
If your TNC allocates a separate callsign to its PMS I suggest
the USER parameter be set to the number of Communications
Windows plus one.
XFLOW ON/OFF
This parameter is important and must be set to reflect the
chosen method of Handshaking that you have specified in paKet's
Serial Port configuration.
For Hardware Handshaking, you must have XFLOW OFF.
For Software Handshaking, you must have XFLOW ON.
Refer to the discussion of Hardware vs Software Handshaking for
more details.
XOFF $13 (Ctrl-S)
XON $11 (Ctrl-Q)
Please leave both these set to their default values.
Page 180
Kantronics TNCs
My comments in this section are directed at the KAM specifically but I
understand other models in Kantronics range operate in a similar manner
so in many cases these comments would most likely apply to the other
models as well.
Several KAM users have written to me about problems, mainly in the area
of Binary File transfers, with the previous version of paKet.
I have only recently had access to a KAM for testing so I am still not
confident the support for these TNCs is as good as it could be.
Just prior to the release of paKet 5 a friend, Col VK2KQX, acquired a
KAM and has successfully tested a Beta version of paKet 5 both for
normal operations and for Binary File transfers.
There are some notable differences in the KAM when compared to other
TNCs, mainly in the area of Multi Stream operation, and these
differences will have an effect on their use with paKet.
*******************************************************
I should point out at this stage, and I want to make it
VERY CLEAR, that I like the KAM from what little I have
seen of it. It is a very nice unit, seems to be very
good quality and has lots of features. I have no reason
to suspect the other models in Kantronics' range are
anything less than first class units. I would like to
have a KAM for myself, so please do not take these
comments in this section as some sort of derogatory
remarks on these TNCs.
*******************************************************
However, because of the differences I have found so far, KAM users
should be aware of some potential operational problems.
Of course there are a considerable number of enhancements in the KAM,
supporting all those other modes such as RTTY, AMTOR, etc. I am not
referring to those changes, but rather to the standard Packet Mode and
the standard commands used by TAPR-compatible TNCs.
paKet was written to suit the standard TAPR TNC (and compatibles) which
was the first of the popular TNCs used in Amateur Radio. They created a
Standard on which all modern TNCs are based. paKet 4 is being used on
thousands of systems around the world with a wide range on TNCs, so it
seems the approach taken has been successful in most cases.
The following differences have been noted in brief testing:
1. STREAMDBL command
Unfortunately the Kantronics range of TNCs do not support the
STREAMDBL command so if you have one of those TNCs you will have to
set paKet's STREAMDBL option OFF.
STREAMDBL is a standard TNC facility to help avoid confusion where
the STREAMSW character is received over the air as part of a data
packet.
For example, the vertical bar character ("|") that is usually used as
the STREAMSW character is also often used as a pseudo graphic
Page 181
character to draw vertical lines or for drawing boxes. When paKet
receives this character from the TNC it must decide whether the TNC
is indicating a change of stream or whether this is just another data
character received over the radio.
TNCs which support STREAMDBL can generate TWO of these vertical bar
characters whenever one is received over the air - then paKet can
tell the difference and there is no confusion.
Without the STREAMDBL feature, you could experience some occasional
(unexpected) changing of streams if you are monitoring the frequency
and happen to receive a STREAMSW character (say a 'vertical bar')
followed by some other character (say 'C'). paKet has no way of
knowing whether the TNC is requesting a change of stream (to stream C
in this example) or if those characters were received over the radio.
In order to support multi stream operations, paKet has no choice but
to assume it is a change of stream!
You could minimise this problem by setting your STREAMSW to some
obscure character that is unlikely to be received in normal
communications. But no matter what character you choose for the
STREAMSW you could still get ANY character combination if monitoring
the frequency while someone else is doing a Binary File transfer and
get what looks like a change of stream!
Another anomaly was detected just prior to release when Col (my faithful
KAM Beta tester) found responses to various commands were going into
a different Communications Window! There has not been a lot of time
to work on this but it seems in Command Mode, the KAM might not
respond to a command on the same stream the command was issued. In
any case, the symptoms are the same, where paKet and the KAM do not
agree on what is the current Stream!
I cannot change the KAM so I cannot prevent these problems from
occurring. However I have added a new command, <Alt-I>, to help tidy
up your display if you do happen to experience these problems on your
system. The <Alt-I> command will initialise the Communications
Windows, clear any backlog in the other Windows, and reset both the
program and the TNC back to the first Stream in the first
Communications Window.
Refer to the <Alt-I> command in the Keyboard Commands section of this
Manual for details.
2. Dual Ports with dual STREAMSW characters.
The KAM's dual port facility introduces another difficulty because
the KAM has TWO ways of indicating a change of Stream - one for each
port!
paKet of course, currently caters for a single STREAMSW character so
if the KAM sends the OTHER STREAMSW character, paKet will take it as
just another data value and pass it through the system!
For either VHF or HF operations, this is not a problem but if
operating both in dual port mode, you will have to manually detect
the change and switch to the other Window if something comes in on
the second port.
Page 182
For example say you had 4 Communications Windows configured in paKet
and are using the first three for VHF communications and the fourth
for HF, you would specify the VHF port's STREAMSW in paKet's Multi
User options. Any changes of Stream between the various VHF sessions
would work normally. If you see the HF port's STREAMSW, you would
have to manually select that Window (eg <Shift-F4>) because paKet
will not recognise the alternate STREAMSW character. It should
automatically detect the normal STREAMSW and switch back to one of
the VHF Windows when something is received on that port.
This procedure has NOT been tested, so any KAM users might let me
know how it handles the Multi Port operation and advise me of any
special techniques you find useful.
A solution to this problem would be to provide support for multiple
STREAMSW characters in paKet but I found out about this a bit too
late to do anything about it for this release. I hope to provide this
support in the next release of paKet.
3. RESET used for soft start
When making changes to the TNC's Communications settings, the usual
procedure is to issue the TNC commands to make the desired changes
then, after making the changes to the computer's serial port the TNC
is initialised to make the new settings effective.
On most TNCs the command to re initialise is RESTART, but on the
Kantronics units the command is RESET. This is not a problem for
paKet because I have added a configurable option in the Serial Port
options to allow you to specify either RESTART or RESET. So if you
are a Kantronics user, just specify RESET for that option and paKet
will issue that command whenever you make any changes to the Serial
Port parameters.
If these things concern you, the only certain way to overcome them is to
use a Host mode program supplied by Kantronics.
With this version of paKet a TNC Help file for the Kantronics range of
TNCs is included. It is a large file, modelled on the other TNC Help
files and again we have Col, VK2KQX, to thank. He probably did not know
what he was letting himself in for when he offered to set up this Help
file, but he stuck with it and has produced this tome for the benefit of
other Kantronics users. Thanks Col.
Page 183
(This page intentionally blank)
Page 184
PART XI - paKet PROTOCOL (pP)
What is pP ?
paKet Protocol, or "pP" for short, is a YAPP-compatible Binary File
Transfer protocol designed especially to provide a Recovery capability
after an aborted file transfer. It is basically the YAPP Protocol with
some additional enhancements to provide the automatic restart capability.
Consider the situation where you are sending a Binary File to another
station and the transfer is aborted for some reason, whether it be a bad
link or power failure or any other reason. You simply send the file
again, using the same <F7> command! With pP, the file transfer will
automatically start from where the previous transfer left off.
pP will mostly be appreciated when you are transferring a large file and
the transfer is aborted when almost finished. For small files, or if a
transfer is aborted near the beginning, you might as well send the
entire file again.
pP may be used to exchange Binary Files with any other station equipped
with either pP or YAPP protocol. The pP protocol automatically detects
the presence of another pP station and will use the enhanced features as
required, otherwise the standard YAPP protocol will be used.
I used the YAPP Protocol Specifications published by Jeff Jacobsen
(WA7MBL), the author of the original YAPP program, when developing this
pP system. Extensive testing has shown pP to be fully compatible with
YAPP Protocol.
At this stage of course, pP is available only with paKet version 5.
However, the paKet Protocol details are offered to the Public Domain and
are discussed in some detail below. I will be happy to assist developers
of other YAPP Protocol software with the pP enhancements so they too can
offer this feature in their software.
But please note, I am offering to discuss the pP *ENHANCEMENTS* to
*EXISTING* YAPP Protocol programs. Please don't call me for assistance
with the development/debugging of Standard YAPP Protocol software!
In the sections that follow, I give some examples of the exchange of
dialog between the two stations. For convenience here, I will refer to
the two sides as the Sender and the Receiver. So, if I use the term
"Sender" or "Receiver" I might be referring to the operator or to the
software or to the system generally, but I am sure you will get the idea.
I hope Jeff Jacobsen will forgive me if I suggest his original YAPP
program has now been superseded but his YAPP Protocol lives on as the
current Standard for Binary File transfers in the world of Packet Radio.
In the following sections, when I refer to "YAPP", I am referring to the
YAPP Binary File Transfer Protocol, not to the original YAPP program
that started it all.
Page 185
Using pP
For most Binary File transfers, pP will behave in a similar manner to
YAPP and the performance will be the same.
No special action is required to use pP. Using pP is the same as using
YAPP so if you have been using an earlier version of paKet, the
procedure to send or receive a Binary File is the same.
Refer to the <F7> and <F8> keys in the "Keyboard Commands" section of
this Manual for operation details.
Typical scenario:
Say you are sending a Binary File to another pP station. You send the
file in the usual way, starting with the <F7> key.
The transfer begins just like any other Binary File transfer starting
from the beginning of the file.
Then part way through, let's say after sending half the file, something
goes wrong. Ummm, for this illustration we'll say the digipeater we were
using goes off the air and we lose the link with the other station.
So, call up using a different path and establish communications with
that station again. Then start the same file transfer again, using the
same <F7> key again, specifying the same filename again. Come to think
of it, this is what you would do anyway, isn't it? Whether using pP or
not! But with most other protocols, the entire file would be resent from
the beginning. With pP, a Recovery is possible.
When the file transfer is started, the following activity takes place
(assuming both stations support pP):
1. The exchange of pP/YAPP initialisation codes verifies each station
is ready to start the transfer (standard YAPP Protocol).
2. The Sender sends the Protocol header, which includes the file name
and file size (standard YAPP protocol). The header also includes a
new field to identify this station as a pP station.
3. The Receiver detects that this file already exists on that system
and is smaller than the one about to be received. (The file is
smaller because it is only half there!)
The Receiver now knows that the Sender is a pP station because of
the additional field in the header.
4. The Receiver requests a pP recovery and sends some details of its
(shorter) file.
5. The Sender checks those details against the file about to be sent.
It looks like the same file, so the Sender issues an approval then
starts sending from the agreed point in the file.
(If the Sender decides it does not look like the same file, the
Recovery request would be denied and the transfer would start from
the beginning).
Page 186
6. When the Receiver gets the Recovery approval, that system will
reset the file pointers and will start writing any data received
at the agreed starting point in the file, effectively appending to
the existing file.
7. The transfer then continues from that point using standard YAPP
Protocol.
While all this is going on, you do nothing - just watch the messages
informing you of the exchange of pP dialogue as outlined above. Then
when the Binary File Transfer Window appears you will see the file
transfer is already partly completed! It has picked up almost from where
it left off.
Page 187
The technical details of the paKet Protocol:
For this discussion I will be referring to some of Jeff Jacobsen's YAPP
Specifications. If you are a developer of YAPP compatible software, you
will already know about these things. If you are an interested user and
do not have these specifications handy, I will try to explain as I go.
A warning though... this section does get a bit heavy and is included
for the technically minded. If you find you are having trouble
understanding it, just skip to another section - it is NOT necessary to
understand all this in order to use pP.
Sender - Sending a pP/YAPP Header
The YAPP Header is listed in the YAPP specifications as follows:
HD Send_Hdr
<SOH> <len> (Filename) <NUL> (File Size in ASCII) <NUL> (Opt)
This header is sent at the beginning of the transfer to identify the
name and size of the file about to be sent. Note there is an optional
field provided, and it is this optional field that pP uses to identify
the Sender as a pP station.
When the Sender sends a file header, the "optional" field will contain
the pP Identifier string, "paKet-Protocol" (without the quotes).
So if we were sending a file "PROG.EXE" and that file was 74692 bytes
long, the pP header might look like:
<SOH><29>PROG.EXE<NUL>74692<NUL>paKet-Protocol
(I use the "< >" combination to indicate single byte values).
This optional field should be sent with every Header. If the Receiver is
running Standard YAPP Protocol it will not get upset because the
optional field is provided for in the Specifications. Testing with
various YAPP Protocol systems has shown this works without problems,
however should some system somewhere object to this optional field being
used in this way, the paKet user can switch off the pP option in the
Configuration - File Transfer options. In that case the Sender would not
send the optional field and the Receiver will think we are running
Standard YAPP Protocol!
Receiver - Receiving a pP/YAPP Header and requesting Recovery
When the Header is received, the Receiver will check the Header's file
details. If that file does not yet exist it will create a new file, send
an <ACK> to the Sender and continue with the transfer using Standard
YAPP Protocol.
If a file of the same name already exists on the Receiver system it
could be just another version of the same file or maybe it is the result
of an earlier transfer attempt that was not completed. If it is a partly
completed copy of an earlier transfer attempt, pP can identify this and
perform a Recovery. If it is not that same file, pP can recognise this
too and revert to Standard YAPP Protocol for a "normal" transfer of the
entire file.
Page 188
The Receiver will request a pP Recovery if the following conditions are
ALL met:
1. a file already exists with the same file name;
and
2. The size of the existing file is greater than 1000 bytes;
and
3. The file size is smaller than that in the Header just received;
and
4. the Header contains the "paKet-Protocol" identifier;
and
5. the user of this Receiver system has indicated in the
Configuration that pP may be used.
(This is implemented in paKet but is an optional feature of the
pP Protocol).
Let's discuss briefly each of these requirements.
1. If the file does not yet exist, there is no need for Recovery and a
standard YAPP Protocol transfer will take place.
2. You will see later that a Recovery does not actually begin from the
end of this short file, but begins 750 bytes back from the end. If
the Receiver's file is shorter than 1000 bytes, it is hardly worth a
Recovery anyway! We might just as well start again from the
beginning.
3. If the Receiver's file is already bigger than the one about to be
sent, it is certainly NOT the result of an aborted transfer of this
same file!
4. If the Header does not contain the pP identifier, the Sender is not
running pP. There is no point in asking a non-pP system for a
Recovery!
5. The paKet user may disable the pP facility, so the ultimate control
remains with the user. This option is provided in paKet but is not a
requirement of the Protocol. Another program that supports pP might
not provide this user option.
If all the above conditions are met and the Receiver decides to request
a Recovery, a "NP" record is prepared and sent to the Sender. This NP
record is defined below:
NP record.
The YAPP Specifications include an NR record for a negative
acknowledgement ("Not Ready" sometimes referred to as NAK). The standard
NR record provides for the <NAK> code followed by an optional "reason"
in ASCII.
Using this format with the optional field to maintain compatibility
with the Standard YAPP Protocol, I have created a new Protocol record
and I called it NP. This new record is:
Page 189
NP pP Recovery request
<NAK><len>paKet-Protocol,(length of file),(first 100 bytes)(last 100 bytes)
- The <NAK> is the ASCII code with a value of 21;
- <len> is the length of the following data;
- The pP identifier string "paKet-Protocol" comes next (14 bytes).
This is the optional "reason" provided for in the YAPP Specifications!;
- The length of the file is actually the length of the file on the
Receiver's system LESS 850 bytes. (Further discussion on this below)
The value is sent as ASCII characters and please note there are commas
before and after these numbers.
So, if the file on the Receiver's system is 53,964 bytes, this field
would contain the following seven ASCII characters:
,53114,
- The first 100 bytes of the short file on the Receiver system;
- The "last" 100 bytes of the short file on the Receiver system.
To get the "last" 100 bytes the Receiver system will move to a position
850 bytes back from the end of the file and read the next 100 bytes
from there. So the last 750 bytes will be ignored and if a Recovery is
successful, those 750 bytes will be overwritten.
This figure of 850 bytes is somewhat arbitrary. I felt it was necessary
to provide SOME overlap to cover the situation where the end of the
short file might be corrupted (it WAS aborted for some reason, don't
forget!). If you are developing your own pP system, feel free to choose
another figure - this affects only the Receiver, so your system can
still perform a Recovery from paKet (or any other pP system). I would
suggest a larger rather than a shorter figure should be chosen if you
wish to change it. You might like to reduce the overlap to save time on
duplicating the data already sent, but keep in mind it takes only a
second or two to send 100 bytes and the Recovery could save many
minutes, maybe an hour! I don't think the user will get upset if it
takes a few seconds to Recover.
So, as an example, an NP record might look like:
<NAK><221>paKet-Protocol,53114,........
(the dots represent the 200 data bytes).
Sender - Processing a Recovery request (NP record) from the Receiver
After sending the Header, the Sender would usually get an RF packet
indicating the other station is now ready to "Receive the File". In that
case the entire file is sent from the beginning in accordance with the
Standard YAPP Protocol.
If the Sender gets the NP packet, it means the other station is
requesting a pP Recovery. It could be they already have part of this
file so it is now up to the Sender to decide whether it is or is not the
same file. Of course the only way to be really sure about this is to
compare the entire file but if we are going to do this we might as well
send the whole thing again!
Page 190
I decided it is a reasonable risk to compare the first 100 bytes of the
two files, then to compare the last 100 bytes of the files. (The "last"
100 bytes in this case would be somewhere in the middle of the Sender's
file.) If these 200 bytes match - same values at the same locations and
the two files have the same name, then pP will accept they ARE the same
file and the Recovery will be approved.
The NP packet includes the size of the file on the Receiver's system,
the first 100 bytes plus the last 100 bytes of that file. So the Sender
system will access the file about to be sent and will compare the first
100 bytes. If they are all the same, it will move down the file to the
location corresponding to the file size given in the NP record. If the
next 100 bytes in the file also match those given in the NP record, a
Recovery will be approved.
If even one byte does not match, the Recovery will be denied.
So, if the Sender approves the Recovery, it will send the "Approval for
Recovery" packet, the "AP" record, which is a new Protocol record and
consists of two bytes:
<ACK><6>
Then it will position the file pointer to the file size given by the NP
record plus 100 bytes. (Those "last" 100 bytes have been matched so
there's no need to send them again.) And the file transfer continues
from that point using Standard YAPP Protocol.
If the Sender denies the Recovery, it will send the "Recovery Denied"
packet, the "DN" record. This too, is a new Protocol record and consists
of 16 bytes to distinguish it from an "ordinary" NAK:
<NAK><14>paKet-Protocol
As the Recovery has been denied, the file will be sent in its entirety
and the transfer will proceed using Standard YAPP Protocol, starting
from the beginning of the file.
Receiver - Processing Response to Recovery request.
This is the final stage of the Recovery process. The Receiver had
requested a Recovery and now will find out whether the Recovery is
approved or denied. The Receiver will get either an Approval (AP record)
or a Denial (DN record). Details of these records are shown in the
previous section.
If the Recovery is approved, the Receiver will adjust the file pointer
to the file size less 750 bytes.
Yes, that's right 750! We moved back 850 bytes into the file to include
the "last" 100 bytes in the the NP record. Now that we have an approval,
we know those "last" 100 bytes are OK so there's no need to transfer
them again. We will start receiving data from AFTER those "last" 100
bytes, overwriting the last 750 bytes in the file. (See comments above
under "NP Record" - you may vary this "setback" figure of 850 bytes if
you are developing your own pP software).
If Recovery is denied, the entire file will be sent so the Receiver will
either have to overwrite the existing file or create a new one.
Page 191
I would like to point out here that if the paKet program is receiving a
file and Recovery is denied, the existing (short) file will be preserved
and a new file with a different extension (eg: .000 or .001 etc) will be
created. This is a feature of the paKet program NOT part of the pP file
transfer Protocol. pP just manages the Recovery process. So if some
other program uses pP it might handle "Recovery Denied" differently by
simply producing an error message such as "File Exists" or it might
overwrite the existing short file.
Page 192
PART XII - ADMINISTRATION DETAIL
The cost of paKet.
paKet is offered to the world as a Shareware product for $25 (Aust) per
copy. If you would like me to mail a copy to you, an additional $5 covers
the cost of a diskette, postage, and packaging.
For those who are unfamiliar with Shareware, let me explain briefly: A
Shareware product is one which may be copied freely and distributed to
others for evaluation. However, if anyone decides to keep and use the
program, the prescribed payment must be paid. It is not a Public Domain
program.
As with most other software products, it is likely there will be many
people who take it and use it illegally, but with Shareware distribution
it is possible to keep the cost down to a minimum, cutting out the middle
men and the costly distribution channels. An equivalent (or lesser!)
commercial product might cost hundreds more because of these overheads. I
think you will agree, $25 is not an exorbitant price for the "best Packet
Radio software in the world".
I hope you are honest enough to pay the $25 if you use paKet.
You can charge the $25 to your Visa, Mastercard or Australian Bankcard.
Or if you prefer you could send a Money Order or a cheque (that's "check"
if you're American). Please send the following Registration Form with
your details.
When you register for paKet, you are registered for life! I will be happy
to send you any updates as they become available, provided I can cover my
costs. So if you would like the next update, send me $5 (or equivalent in
your currency) to cover the cost of a diskette, mailer box, postage,
etc. Perhaps you should wait until a new version is announced before
sending your $5 because I am not sure how many more versions there will
be!
Please let me know what you think of paKet and let me know if you have
any ideas for improvement. While I cannot promise to incorporate all
suggestions, your opinions and ideas are welcomed. Of course I would also
like to know if you detect any .. er .. bugs .. in the system.
Page 193
Acknowledgements and Credits
I would like to acknowledge here the help, enthusiasm, encouragement and
support I received from a large number of paKet users, especially the
local Packet/paKet users who have inspired me to continue developing
paKet.
Paul VK2BZC, has been and continues to be a powerful force in the
development of the paKet system. He has a rare blend of expertise,
intelligence and ideas. This, combined with an enthusiasm for paKet that
must come close to matching my own, has resulted in a continual flow of
critical comment that has proved to be of enormous benefit to the
finished product. Thanks Paul.
Col VK2KQX, the poor unsuspecting fellow who mentioned to me that he had
bought a KAM. Since then Col has done a lot of testing with the Beta
version of paKet 5 proving the Binary Transfer system, firstly with his
BayCom system then with the KAM after he upgraded. Col also provided his
professional expertise in getting the diskette labels and mailer boxes
prepared and printed, going way beyond any reasonable call of duty. If
that was not enough, he also volunteered to prepare the TNC Help File for
the Kantronics range of TNCs, a mammoth task that I am sure will be
appreciated by all users of these TNCs.
And the list goes on ... Daryl VK2DAZ, provided lots of help, advice and
testing with paKet's Script processing; Arthur VK2ATM, for help with Beta
testing and for making his system available for our local BBS; Bill
VK2ZCV, a devoted Digicom then BayCom user, for help with testing the
Digicom and BayCom file transfers.
A special mention of thanks is due to Chris Edmondson VK3YID, editor of
the Amateur Radio Action magazine for a most complimentary review of
PAKET 4 and for carrying a classified advertisement for paKet, month
after month.
And there are the literally hundreds of paKet users who have written with
support, advice, suggestions and encouragement. A large number of the
improvements in this version of paKet have come from the paKet community.
Although so many people have contributed so much, I want to emphasise
that any problems you have with paKet are my fault because I did the
programming.
Page 194
Where to find the author
All packet radio communications can be sent via the Packet Network to me,
Tony VK2DHU @ VK2ATM.NSW.AUS.OC. When you "write", please tell me which
version of paKet you are using and the type of TNC you have. I reply to
ALL mail but on several occasions I have discovered (upon investigating
queries) that mail sent to me via Packet Radio has not arrived. If you do
not get a reply, please send a follow up note.
All mail communications, including the $25, may be sent as follows:
M. A. Lonsdale,
VK2DHU,
6 Marsden Cres,
Port Macquarie 2444
Australia
I am NOT on the phone (if you get my drift).
Please use and enjoy paKet, and if you give a copy to your friends,
please give them all the original files to ensure they get the full
paKet system.
And don't forget to let me know of your experiences with paKet.
73s
de Tony VK2DHU
Page 195
REGISTRATION FORM
paKet version 5.0
Name___________________________________________________________________
Call Sign_____________________Home BBS for Packet Mail_________________
Address________________________________________________________________
________________________________________________________________
Type of TNC____________________________________________________________
Diskette Type: 360KB [ ] 1.2MB [ ] 720KB [ ] 1.44MB [ ]
(5.25 inch) (3.5 inch)
Where did you get paKet (optional)?
BBS? _______________________________________________________________
Friend? _______________________________________________________________
Comments_______________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
-----------------------------------------------------------------------
Make cheques (checks) payable to:
M. A. Lonsdale
Address:
6 Marsden Crescent, Port Macquarie, NSW 2444, Australia
-----------------------------------------------------------------------
Payment:(mark or circle one):
[ ] Cheque [ ] Money Order [ ] Cash
[ ] Visa [ ] MasterCard [ ] Bankcard
Credit Card #_________________________________________Amount $A_______
Expiry Date___________________Signature ______________________________